Hi,
Based on the test results from --debug-configuration, your newer
version of Boost must have all of the following:
libboost_system-mt.a
libboost_thread.a
libboost_program_options-mt.a
libboost_unit_test_framework-mt.a
libboost_iostreams-mt.a
There's not much we can do to stop the compiler from linking against
system libraries if they exist, as we need zlib and friends. Could add
an option to bjam that would look for the versioned names of Boost
libraries.
Kenneth
On 07/16/12 08:59, Aleksandr Belyaev wrote:
> Hello Kenneth,
>
>> - Have you updated Moses since Tue Jul 3 12:14:41 2012 -0400? Alex
>> Fraser mentioned a similar issue with Boost 1.50 and I checked in a fix.
> Yes, I have the latest version of the moses from Github.
>
>> - You might have multiple versions of Boost installed. Theoretically,
>> it's possible to compile Moses under this scenario, but you have to
>> ensure that your new install has a superset of the libraries that your
>> old install has.
> I'm trying to compile on the cluster where I dont have access to root account,
> so there's old version of boost (I've tried with it too without any success),
> but I directly set a path to Boost by --with-boost option. Isn't it enough?
>
>> Also, it would help if you run with -d2 --debug-configuration .
> Tried this one, results are quite same as the last ones -
> http://pastebin.com/bq2LuDh8 .
>
>
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
