This is the mail archive of the libc-hacker@cygnus.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: glibc in cvs failed to build



Hello,

On Sat, May 01, H.J. Lu wrote:

> glibc in CVS as of May 1 at 1pm failed to build on Intel. I am using
> egcs 1.1.2, adding -mcpu=pentiumpro -march=pentiumpro.
> 
> 
> -- 
> H.J. Lu (hjl@gnu.org)
> ---
> /work/build/gnu/bin/glibc/elf/ld-linux.so.2 --library-path /work/build/gnu/bin/glibc:/work/build/gnu/bin/glibc/math:/work/build/gnu/bin/glibc/elf:/work/build/gnu/bin/glibc/nss:/work/build/gnu/bin/glibc/nis:/work/build/gnu/bin/glibc/db2:/work/build/gnu/bin/glibc/rt:/work/build/gnu/bin/glibc/resolv:/work/build/gnu/bin/glibc/linuxthreads /work/build/gnu/bin/glibc/sunrpc/rpcgen -Y `gcc -pipe -mcpu=pentiumpro -march=pentiumpro -print-file-name=cpp | sed "s|/cpp$||"` \
> 	      -h rpcsvc/bootparam_prot.x -o /work/build/gnu/bin/glibc/sunrpc/rpcsvc/bootparam_prot.T
> /work/build/gnu/bin/glibc/sunrpc/rpcgen: Cannot allocate memory
> make[2]: *** [/work/build/gnu/bin/glibc/sunrpc/rpcsvc/bootparam_prot.stmp] Error 1
> make[1]: *** [sunrpc/others] Error 2

Are you using a machine with 2GB RAM ? I had the same problem here
with a patched kernel for 2GB RAM, booting a kernel which allows
only 960MB RAM solved the problem. No recompiling was necessary.
So I'm not sure if it is a kernel problem.

  Thorsten

-- 
Thorsten Kukuk      http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE GmbH           Schanzaeckerstr. 10             90443 Nuernberg
Linux is like a Vorlon.  It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]