x86_64-pc-linux-gnu/bin/ld:
.../lib64/libboost_system-mt-1_37.a(error_code.o): relocation R_X86_64_32S
against `a local symbol' can not be used when making a shared object;
recompile with -fPIC
.../lib64/libboost_system-mt-1_37.a: could not read symbols: Bad value
You do not need to have boost available as a shared library.
Sorry Jan, I don't understand - how can I link my library in with the user's
local installation of Boost if it's not available as a shared library?
I do not truly have an answer for that. But if I remember correctly,
I had seen ".pic.a" libraries previously which, I would say,
would alleviate the problem, short of them being much less widespread
in use than .a archives already are.
It really seems uncommon to me for users not to have shared libraries
these days..
Sorry, I should've expressed that more clearly - I didn't think it was
possible to link with a user's local installation of Boost if it wasn't in
shared-library form.
I have Boost installed on my system as a shared library, so I don't understand
why libtool/gcc won't link to it.
Thanks,
Adam.
