Re: Problems compiling glibc 2.2.* with kernel headers

[Justin Palmer]

Please CC newsgroup as my news server is not set up.


On Fri, 1 Nov 2002, Mike Castle wrote:

> In article <address@hidden> you write:
> >GNU GCC 2.95.3
>
> Unsupported, I believe.  Be sure to read all of the docs before trying
> this.
>
> mrc
>
> --
>      Mike Castle      address@hidden      www.netcom.com/~dalgoda/
>     We are all of us living in the shadow of Manhattan.  -- Watchmen
> fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
>


>From the INSTALL file included with both packages:

"GCC 2.95.3 is the compiler we advise to use."


On Sat, 2 Nov 2002, Wolfram Gloger wrote:

> > For glibc with 2.4.19 linux headers, I get:
> >
> > make[1]: Entering directory `/tmp/glibc-2.2.*/malloc'
> > ...
> > memusagestat.c:36: gd.h: No such file or directory
>
> Try configuring --without-gd.  I always do.


This configuration option allowed the make to complete without errors for
glibc 2.2.4.  What does it do and why is there no documentation about it?


The make check now fails, however, on globtest.  Any thoughts?

make[1]: Entering directory `/tmp/glibc-2.2.4/posix'
...
/bin/sh -e globtest.sh ../ ../elf/ \
         ld-linux.so.2
cmp: EOF on -
make[1]: *** [globtest.out] Segmentation fault (core dumped)


I'm also disturbed at seeing this repeated output:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_US"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").


If these macros need to be set by the user, it should be in the
documentation (eg INSTALL).  They are warnings, so I guess it can slide.

Any more assistance with the make check failures would be appreciated.
I'm not sure why it's so difficult to build such a vital software
component after following the described installation process.  Am I
missing something?  Doesn't Red Hat 8.0 use glibc 2.2.5 with a recent
kernel (2.4.18)?  Perhaps my problems reflect why they aren't using kernel
2.4.19 or higher.


Thanks,
Justin

address@hidden