2011/9/3 Jonathan Wakely <jwakely.gcc@xxxxxxxxx>: >> Any ideas why the RPATH might be missing? > > This is a FAQ, read the docs. Your dynamic linker doesn't look in /opt/csw > and gcc does not use a rpath automatically. Building gcc is not trivial, > read the docs! Carefully! I have read the docs. The configuration stage instructions explain this part: "...also the --with-mpc=mpcinstalldir option is shorthand for --with-mpc-lib=mpcinstalldir/lib and --with-mpc-include=mpcinstalldir/include" On my system, these locations are correct, the following files exist: /opt/csw/include/mpc.h /opt/csw/lib/libmpc.so -> libmpc.so.2.0.0 /opt/csw/lib/libmpc.so.2 -> libmpc.so.2.0.0 I assumed that the information about libmpc.so.2 location is passed to the intermediate binaries. You linked to a FAQ item about the runpath[2], if I understand correctly, it doesn't concern building/bootstrapping GCC, it's about binaries built by GCC. It says that if e.g. libstdc++.so.6 is in /opt/foo, you need to compile your binary with the -R/opt/foo option (at least on some systems). In case of the GCC bootstrap, it runs ./configure subinvocations, and I would assume that it knows about passing the -R flag. > It's much easier to build gmp, mpfr and mpc statically by putting them in > the gcc source tree. Thanks for the hint. So far, I have intentionally avoided this, preferring the divide-and-conquer model. Porting to Solaris can be tedious, so I generally prefer to build the dependencies once and be done with it. Interestingly, with the identical build options, it succeeded on one machine and failed on the other. I'm currently running two additional builds and will post information when they're finished. Maciej [1] http://gcc.gnu.org/install/configure.html [2] http://gcc.gnu.org/faq.html#rpath
