> This has to be a libtool bug.  When I ask gcc where
> libstdc++.la
> lives, I get:
> 
> [EMAIL PROTECTED]:/builds/wesolows $
> /tonic/gcc-tools/i386/gcc-3.4.3/bin/gcc
> --print-file-name=libstdc++.la
> /tonic/gcc-tools/i386/gcc-3.4.3/bin/../lib/gcc/i386-pc
> -solaris2.10.1/3.4.3/../../../libstdc++.la

$ gcc  --print-file-name=libstdc++.la
/opt/gcc-3.4.3/bin/../lib/gcc/i386-pc-solaris2.10.1/3.4.3/../../../libstdc++.la

But inside /opt/gcc-3.4.3/bin:

$ grep wesolows *
gccbug:configured with: ../gcc-3.4.3-csl/configure 
--prefix=/builds/wesolows/x86/gcc-3.4.3 
--with-local-prefix=/builds/wesolows/x86/gcc-3.4.3 --enable-threads=posix 
--with-as=/usr/sfw/bin/gas --with-ld=/usr/ccs/bin/ld --with-gnu-as 
--without-gnu-ld --enable-languages=c,c++ --enable-shared

and

$ cd ../lib
$ grep wesolows *
libstdc++.la:dependency_libs=' 
-L/builds/wesolows/gcc-build/i386-pc-solaris2.10.1/libstdc++-v3/src 
-L/builds/wesolows/gcc-build/i386-pc-solaris2.10.1/libstdc++-v3/src/.libs -lm 
-lm -lm -L/builds/wesolows/gcc-build/gcc -lgcc_s -lgcc_s -lm -lgcc_s -lgcc_s'
libstdc++.la:libdir='/builds/wesolows/x86/gcc-3.4.3/lib'
libsupc++.la:dependency_libs=' 
-L/builds/wesolows/gcc-build/i386-pc-solaris2.10.1/libstdc++-v3/src 
-L/builds/wesolows/gcc-build/i386-pc-solaris2.10.1/libstdc++-v3/src/.libs -lm 
-L/builds/wesolows/gcc-build/gcc -lgcc_s -lgcc_s'
libsupc++.la:libdir='/builds/wesolows/x86/gcc-3.4.3/lib'

so I think that libtool is not *that* wrong. But at other places, with other 
sources, it finds the right things...

> which happens to be where I've installed the compiler
> (and the file's
> there).  I can't get it to print
> /builds/wesolows/anything.

Try a look inside the .la files. Is there your path? It could be that the 
problem is at gcc configuration scripts. I did not try to fix it with the .la 
things, since the simple symlink workaround was ok for me.

>  My
> apologies for the trouble.

This was no trouble. It was interesting for me to investigate, since I never 
took a closer look to gcc in this direction before. Also it really occured only 
with glibmm and gtkmm as far as I've tested. I've compiled a lot of things 
without gcc related problems - eg. X11, Qt, lots of tiny tools...

Gruesse,
Helmar
[EMAIL PROTECTED]
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to