Hi,
So uh Boost 1.53.0's version.hpp says
#define BOOST_VERSION 105300
That's not what yours says. You can run
g++ -x c++ -E /dev/null -include boost/version.hpp -v
to figure out where it found boost/version.hpp. For example, mine says
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/include/g++-v4
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/include/g++-v4/x86_64-pc-linux-gnu
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/include/g++-v4/backward
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/include
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/include-fixed
/usr/include
End of search list.
# 1 "/dev/null"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "/usr/include/boost/version.hpp" 1 3 4
# 1 "<command-line>" 2
# 1 "/dev/null"
and so the location is /usr/include/boost/version.hpp in my case. Then
go to your sysadmin and ask why it's not 1.53.0. . .
Kenneth
On 06/12/13 10:48, Felipe Sánchez Martínez wrote:
> Hi Kenneth,
>
> Thanks for your reply.
>
>> g++ -dM -x c++ -E /dev/null -include boost/version.hpp 2>/dev/null |grep
>> '#define BOOST_VERSION'
>
> #define BOOST_VERSION 103301
>
>> - What is your bjam command line?
>
> bjam --with-irstlm=$DIR/local --with-giza=$DIR/local/bin -j4
>
>
>> - What is the output of this command?
>
> You have Boost 103301. Moses requires at least 103600 (and preferably
> newer).
>
> bjam version is:
>
> Boost.Build 2011.12-svn
>
>
> Thanks in advance for your help.
> Regards
> --
> Felipe
>>
>> equery belongs /usr/include/boost/version.hpp
>>
>> Kenneth
>>
>> On 06/12/13 04:52, Felipe Sánchez Martínez wrote:
>>> Hello all:
>>>
>>> I am compiling moses on a cluster running gentoo that has libboost
>>> 1.53.0 (last version available), but when I try to compile bjam says:
>>>
>>> "You have Boost 103301. Moses requires at least 103600 (and preferably
>>> newer)."
>>>
>>> I guess that those numbers refer to the SVN revision of the library.
>>>
>>> The version of moses I am using dates back April 2012 and I have
>>> compiled it without problems with libboost 1.48.
>>>
>>> Any ideas of how to solve the problem that does not involve reinstalling
>>> liboost (I do not have root privileges on that machine)?
>>>
>>> Thanks a million!
>>> Regards.
>>>
>> _______________________________________________
>> Moses-support mailing list
>> [email protected]
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support
