On Thursday, 24. February 2011 12:23:29 Christopher Jefferson wrote:
On 24 Feb 2011, at 10:14, Cedric Laczny wrote:
Sorry, my bad. Hit "Send" before being finished...
So let's start again... I apologize.
Hi,
I have a program that uses serialization-functionality for some of the self- defined classes. I specify "-lboost_serialization" with the g++ and it works fine on my local machine. However, when I want to compile it on a remote machine, it fails. The remote machine is lacking >=boost-1.42 which is needed. Therefore I built (no install) boost-1.45 remotely (under /local/cedric/boost_1_45_0) and at least the configure-script (generated using autotools) seems to detect all the necessary libraries and headers (provided I specify them in the environment variables), on my local machine aswell as on the remote machine. Now the problem is, that I don't find the reason why it fails to compile my program remotely... Any ideas?
Here's the command used for linking: /bin/bash ../libtool --tag=CXX --mode=link g++ -Wno-deprecated -g -O2 - lboost_serialization -L/local/cedric/boost_1_45_0/stage/lib -o test test- main.o ../includes/Parser/libparser.a -lgsl -lgslcblas -lm
This might not be your problem, but I have seen issues like this when the included headers and linked libraries are not in sync with each other. Make sure you are both picking up the right headers, and the right library files.
I know this should be rather done in the opposite direction (correct configuration at the beigninning), but can you tell me how I can find out, which versions were actually used? I know about "ldd" which AFAIK only works for executable binaries. Your point sounds reasonable to me in my scenario and this might help me track down the issue... Thank you.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users