Re: [Boost-build] default compiler paths on 64 bit linux

Subject: Re: [Boost-build] default compiler paths on 64 bit linux
From: Vladimir Prus (ghost_at_[hidden])
Date: 2010-10-23 03:45:00

On Wednesday, October 20, 2010 14:56:34 Avi Bahra wrote:
> It looks like the default compiler paths on linux 64 are not correct ?
> 
> bjam -d2
> ...patience...
> ...patience...
> ...patience...
> ...found 12338 targets...
> ...updating 2 targets...
> gcc.link bin/gcc-4.3/debug/embedding
> 
>     "g++" -L"/usr/lib" -L"/usr/lib/python2.6/config" -Wl,-R
> -Wl,"/usr/lib" -Wl,-R -Wl,"/usr/lib/python2.6/config" -Wl,-R
> -Wl,"/vol/ecf/boost/boost_1_43_0/bin.v2/libs/python/build/gcc-4.3/debug"
> -Wl,-rpath-link
> -Wl,"/vol/ecf/boost/boost_1_43_0/bin.v2/libs/python/build/gcc-4.3/debug"
> -o "bin/gcc-4.3/debug/embedding" -Wl,--start-group
> "bin/gcc-4.3/debug/test/TestEmbedded.o"
> "/vol/ecf/boost/boost_1_43_0/bin.v2/libs/python/build/gcc-4.3/debug/libboos
> t_python.so.1.43.0" -Wl,-Bstatic  -Wl,-Bdynamic -lpython2.6 -lutil
> -lpthread -ldl
> -Wl,--end-group -g
> 
> 
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libutil.so when searching for -lutil
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libutil.a when searching for -lutil
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libpthread.so when searching for
> -lpthread
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libpthread.a when searching for
> -lpthread
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libdl.so when searching for -ldl
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libdl.a when searching for -ldl
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libm.so when searching for -lm
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libm.a when searching for -lm
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libc.so when searching for -lc
> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
> skipping incompatible /usr/lib/libc.a when searching for -lc
> gcc.link bin/gcc-4.3/debug/embedding_ecf
> 
> 
> How would I add -L/usr/lib64 on the link line ?

There's <library-path> feature in documentation, I think. However, I don't 
think that's either right question, or the answer that will help you -- 
there's no error above, only warnings, so you probably wanted to ask
"how to REMOVE /usr/lib from the link line"?

This /usr/lib comes from python.jam:compute-default-paths. Regretfully,
I don't see any way to ask 'python' about the location where its libraries
are installed. There's sys.exec_prefix, but no sys.lib_prefix. Do you
know any way?

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build: http://boost.org/boost-build2