On Tue 06-08-15 22:12, Paul Eggert wrote:
> Keith Thompson <[EMAIL PROTECTED]> writes:
>
> > I got the same error with gcc 4.1.1.
>
> Are you building GCC with the Sun linker, or with the binutils linker?
> I'm doing the former, and that might be related to the problem. Not
> that I think it matters, but I built GCC 4.1.1 with
> "CONFIG_SHELL=/bin/ksh configure --disable-nls
> --enable-languages=c,c++ --with-system-zlib --prefix=[my local
> prefix]"
It looks like I'm using the GNU linker; "gcc -v" says
"GNU ld version 2.16.1".
[...]
> > I'm trying again with PATH=`getconf PATH` (which sets it to
> > /usr/xpg4/bin:/usr/ccs/bin:/usr/bin:/opt/SUNWspro/bin). This will
> > use Sun's C compiler rather than gcc.
And it worked.
> Good luck. But it should work with GCC 4, since it works for me.
>
> Can you reproduce the problem with the following small program?
> What happens when you try to compile and link it with GCC?
>
> char gai_strerror ();
>
> int
> main ()
> {
> return gai_strerror ();
> }
>
> On my host "gcc t.c -lsocket -lnsl" compiles and links this just fine.
Mine too.
I've been messing around with $LD_LIBRARY_PATH and $LD_RUN_PATH;
possibly that screwed things up somehow.
--
Keith Thompson (The_Other_Keith) [EMAIL PROTECTED] <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
