[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (no subject)
From: |
Axel Kittenberger |
Subject: |
Re: (no subject) |
Date: |
Thu, 24 Jan 2002 08:32:13 +0100 |
> I've tryed to compile glibc 2.2.5 on my Linux box (RedHat 7.0) and got the
> following:
>
> ../elf/ld-linux.so.2 --library-path
> ..:../math:../elf:../dlfcn:../nss:../nis:../rt:../resolv:../crypt:../linuxt
>hreads ./rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o
> xbootparam_prot.T execv: Permission denied
> ./rpcgen: C preprocessor failed with exit code 1
> make[1]: *** [xbootparam_prot.stmp] Error 1
> make[1]: Leaving directory `/home/Nick/src/glibc-2.2.5/sunrpc'
> make: *** [sunrpc/others] Error 2
>
> I have gcc version 2.96 20000731, glibc 2.2.4, kernel 2.4.17.
>
> What could it be?
Take a look where /lib/cpp is pointing at, it's normally a link to the
"system" preprocesser rpcgen uses. Most people (including me) forget to
update the symlink when updating/replacing the system compiler.
> And the next question: if I use gcc 3.0.3 fo compling system-wide glibc,
> will it break existing applications (and possibly all the system)?
Everything you do mess around with vour default libc can quikly break your
system globally :o) (In example I had very funny effects that new compiled
apps do no link, but I installed the new glib in /usr/local only, thought it
would be safe, however gcc seems to prefer /usr/local/include over
/usr/include, out of what reasons ever. )
- Axel