From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-10 06:52:17
On Friday 10 March 2006 13:32, Markus Schöpflin wrote:
> Because if you have multiple gcc versions installed side-by-side, you have
> to make sure that the dynamic libs matching the compiler version are
> For example:
> > ldd bind_visit_test
> Main => bind_visit_test
> libstdc++.so.6 => /opt/gcc-4.0.2/lib/libstdc++.so.6 (*)
> libm.so => /usr/shlib/libm.so
> libgcc_s.so.1 => /opt/gcc-4.0.2/lib/libgcc_s.so.1 (*)
> libc.so => /usr/shlib/libc.so
> The libs marked by (*) are dependent on the compiler version, hence the
> library loader path must be adjusted depending on the compiler version.
Are there libraries with the same name in different locations? It seems Debian
somehow solves this problem...
> > BTW, can you also tell how you configure gcc-4.0.2 with V1? That is,
> > what's the content of the toolset file?
> local GCC_ROOT_DIRECTORY = "/opt/gcc-4.0.2" ;
Anyway, OS differences do not matter. I've checked in a patch that should make
this work automatically with V2. Can you try again?
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk