Hi Lane That's puzzling. It works when I set --with but not --enable. That is a slightly odd combination - you are telling moses where boost is but you don't want it to use it - but it shouldn't cause a compile error.
I fixed a small bug in configure.in which meant that threading was always on. Probably not connected though. The logic of configure.in has got rather convoluted. cheers - Barry On Monday 23 May 2011 20:16:18 Lane Schwartz wrote: > Turns out the solution is to set --enable-boost. Once I do that things > configure and compile correctly. > > In my previous unsuccessful attempts, I must have been setting --with-boost > but not --enable boost. > > Cheers, > Lane > > On Mon, May 23, 2011 at 5:29 AM, Barry Haddow <[email protected]> wrote: > > Hi Lane > > > > On our servers the boost libraries are in /usr/lib64 and it works find. > > Could > > you run > > > > ls -l /usr/lib64/libboost_* > > > > and send me the output? > > > > cheers - Barry > > > > On Monday 23 May 2011 10:25, Barry Haddow wrote: > > > Hi Lane > > > > > > Looking at the macro, it should check /usr/lib64, so I don't know why > > > > it's > > > > > not finding the boost libraries for you. > > > > > > The usual problem with centos is that it has a very old automake - did > > > > you > > > > > install an up-to-date one? > > > > > > Could you send me your config.log ? > > > > > > cheers - Barry > > > > > > On Friday 20 May 2011 19:22, Lane Schwartz wrote: > > > > I'm running on Centos 5, and as such have an older version of boost > > > > 1.39 > > > > > > in /usr/include, with the boost libraries in /usr/lib64. > > > > > > > > In older versions of Moses, I was able to compile Moses with boost by > > > > providing a flag to configure --with-boost-libdir=/usr/lib64. This > > > > option > > > > > > is no longer present in trunk. > > > > > > > > In the current version of trunk, the only relevant option seems to > > > > be --with-boost. When I run configure without this option, configure > > > > correctly finds the headers in /usr/include, but make fails to find > > > > the libraries in /usr/lib64. When I run configure with > > > > --with-boost=/usr/lib64, configure fails to find the headers > > > > (presumably > > > > > > because it's looking for them in /usr/lib64!). > > > > > > > > The old way of being able to specify just the libdir for boost was > > > > exactly what I needed. Does anyone know why this option disappeared? > > > > Or know of a current way to compile in this situation? > > > > > > > > Thanks, > > > > Lane > > > > -- > > The University of Edinburgh is a charitable body, registered in > > Scotland, with registration number SC005336. > > > > _______________________________________________ > > 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
