Re: Ugly missing symbols, was Re: egcs, Irix6 linking o32-libiberty.a with n32-stage2/3 binaries ...

[Lee Iverson <leei at ai dot sri dot com>]

In message <01BE22B5.C449D2F0.pedwards@ball.com> you write:
> 
> mv tlist piclist
> /usr/local/src/building/here/gcc/xgcc
>   -B/usr/local/src/building/here/gcc/
>   -g -O2 -fno-implicit-templates -mabi=64 -shared
>   -o libstdc++.so.2.9.0 `cat piclist` -lm
> ld64: FATAL 9: I/O error (-lm): No such file or directory
> collect2: ld returned 32 exit status
> gmake[4]:  *** libstd++.so.2.9.0 Error 1
> 
> 
> The "target trace" printed back from gmake at this point was 
> libstd++.so.2.9.0, multi-do, multi-all, all-target-libstdc++, bootstrap.
> 
> Obviously, libm isn't being found.  I discovered it under /usr/lib and 
> /usr/lib32, but since -mabi=64 is being specified, the linker searches 
> /usr/lib64, which has no libm.*.
> 
> (I'm wondering whether specifying CC='cc -n32' was even worth it, given that 
> the build process seems to prefer -64.)
> 
> God, I hate SGIs.

I'm a fan, but this is really an egcs problem (without an obvious
fix).  egcs is trying to do a full multilib build but without first
testing that it can do it.  Most SGI users don't *ever* build -64
programs and thus don't even install any of the -64 libraries or
support software.  Yet, egcs doesn't check this before deciding that
it should build -64 multilib versions...

The short answer is that you need to install (at least)
compiler_eoe.sw64.lib from the Development Libraries CD.  Ideally
there'd be a way of selecting multilib variations to compile at the
`configure' level of egcs.

-------------------------------------------------------------------------------
Lee Iverson     		SRI International
leei@ai.sri.com			333 Ravenswood Ave., Menlo Park CA 94025
http://www.ai.sri.com/~leei/	(650) 859-3307