From: Robert L Cochran <cochranb@speakeasy.net>
To: Colin Harris <charis.g3orh@virgin.net>,
Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: Redhat 8 or 9 modules ?
Date: 21 Apr 2003 21:04:00 -0400 [thread overview]
Message-ID: <1050973440.3572.12.camel@bobcp4.lingpgmr.com> (raw)
In-Reply-To: <002301c307d3$cc2e8300$14000a0a@p75>
The initial release of Red Hat 8.0 had a problem with glibc that might
be affecting you here. There have been several updated glibc releases
for recent Red Hat distributions including 8 and 9.
I strongly suggest first updating your Red Hat 8 or 9 system with all
the current bug fixes and updates before attempting to compile anything.
I definitely don't try compiling myself unless all the Red Hat bug fixes
are installed on my system.
Also, if you use CPAN to fetch and compile Perl modules under Red Hat 9,
see Red Hat's Bugzilla bug #87682, and use the suggested workaround
mentioned in that for LANG before you do anything with CPAN. Be very
careful about messing with your LANG/locale settings though. I'd
probably change them back to what they were when I finish downloading
Perl modules off CPAN.
Thanks
Bob Cochran
Greenbelt, Maryland, USA
On Mon, 2003-04-21 at 03:00, Colin Harris wrote:
> Hi all,
> Can anyone out there shed some light please. A
> colleague has high speed access to inet. He downloaded RH
> 8.0 with a copy on CD's for me. Apart from some screen
> anomalies , RH 8.0 compiles with ax25 BUT it * will NOT
> make_modules * and complains that file devlist.h is missing.
> He has just downloaded RH 9.0 himself , which compiled , but
> he says that HE now has the make_modules failure ( devlist.h
> missing ). What IS going on ?
> Has anyone else ( with RH 8.0 or 9.0 ) had this
> persistent failure to make modules and know's the answer ?
> I did ask once before but the only reply I got was from an
> 8.0 user who said he didn't have devlist.h on his system
> either but it made modules ok.
>
> ( Is Redhat going down the plug hole ? ).
>
> - Regards Colin
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Bob Cochran
Greenbelt, Maryland, USA
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2003-04-22 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 7:00 Redhat 8 or 9 modules ? Colin Harris
2003-04-22 1:04 ` Robert L Cochran [this message]
2003-04-23 8:02 ` terry
2003-04-23 7:38 ` terry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1050973440.3572.12.camel@bobcp4.lingpgmr.com \
--to=cochranb@speakeasy.net \
--cc=charis.g3orh@virgin.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox