and I'd try removing the existing libboost package first (looks it's there) before reinstalling. That's to avoid getting the 'already installed' message in case of a broken installation
On Mon, Jul 12, 2010 at 8:04 AM, kk yap <yap...@stanford.edu> wrote: > Hi Nikhil, > > More specifically, you can try libbooost-dev, libboost-filesystem-dev > and libboost-test-dev. > > Regards > KK > > On 12 July 2010 03:55, James "Murphy" McCauley <jam...@nau.edu> wrote: > > I am guessing this is a bug in the autoconf boost detection code. I'd > > try the following: > > First, apt-get install libboost-all-dev > > If that doesn't work, try manually setting the boost paths with the > > appropriate configure options (--with-boost=<path> and friends). > > If that still doesn't work, could you post your config.log (or the tail > > end of it anyway)? > > > > -- Murphy > > > > On Mon, 2010-07-12 at 01:50 -0700, Nikhil Handigol wrote: > >> I recently tried a fresh NOX installation from the noxrepo git repo on > >> Ubuntu 10.04. > >> > >> > >> "./configure --with-python=yes" fails with an error: > >> > >> > >> "configure: error: Could not link against !" > >> > >> > >> The last few lines of the output are: > >> checking for g++ option to produce PIC... -fPIC -DPIC > >> checking if g++ PIC flag -fPIC -DPIC works... yes > >> checking if g++ static flag -static works... yes > >> checking if g++ supports -c -o file.o... yes > >> checking if g++ supports -c -o file.o... (cached) yes > >> checking whether the g++ linker (/usr/bin/ld) supports shared > >> libraries... yes > >> checking dynamic linker characteristics... GNU/Linux ld.so > >> checking how to hardcode library paths into programs... immediate > >> checking for fdatasync... yes > >> checking for ppoll... yes > >> checking for boostlib >= 1.34.1... yes > >> checking whether the Boost::Filesystem library is available... yes > >> configure: error: Could not link against ! > >> > >> > >> > >> > >> This is most likely not a NOX problem, as I have compiled the source > >> multiple times in the past, but on Debian machines. If anyone has > >> encountered a similar problem on Ubuntu and managed to fix it, please > >> let me know. > >> > >> > >> Thanks, > >> Nikhil > >> > >> _______________________________________________ > >> nox-dev mailing list > >> nox-dev@noxrepo.org > >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > > > > > > > _______________________________________________ > > nox-dev mailing list > > nox-dev@noxrepo.org > > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
