Ticket #41 (closed defect: fixed)

Opened 1 year ago

Last modified 4 months ago

config.pl exits with boost error - boost::filesystem::exists()

Reported by: vijaykiran Assigned to: patrick
Priority: major Milestone:
Component: Build System Version:
Keywords: Cc:
Completion:

Description

Hello, I am trying to build juggler 2.2 on fedora 7 (32 bit) since there are no pre-built binaries available for download. I am trying to configure juggler with the following options and I get a boost file system error and the configure stops. Here is the configure statement I issued: 

../configure.pl --prefix=/usr/local/Juggler2.2 --with-audiere --with-boost-fs-lib=boost_filesystem --with-boost-includes=/usr/local/include --with-boost-signals-lib=/usr/local/lib --with-boost=/usr/local --with-cppunit --with-java-orb=JDK --with-jdkhome=/usr/local/j2re1.4.2_15 --with-libusb=/usr/lib --with-nspr-includes --with-nspr-libs --with-nspr --with-nsprver=4.1 --with-opengl=/usr --with-perl=/usr --with-python=/usr --with-gmtl

The error I've got was: 

checking whether Boost version is >= 1.31.0... yes (version 1.34.0)
...
...
...
checking for boost::filesystem::exists() in boost_filesystem in /usr/local/lib... no
configure: error: *** Boost.Filesystem required by VPR ***
make[2]: *** [Makefile] Error 1
make[1]: *** [recursive] Error 1
make: *** [build] Error 2

I have compiled and installed boost and /usr/local/lib is flooded with libboost libraries. I am completely lost as to why this is happening. I remember going into a similar problem an year ago and -with-boost-fs-lib=boost_filesystem magically solved the problem. Most of the boost filesystem library files look like libboost_filesystem-gcc41.so in my /usr/local/lib. Can anyone let me know how to solve it?

Also, I am not too sure if this is the right place to ask these kind of questions. Please let me know if it is not.

Thanks, Vijay.

Attachments

Change History

07/23/07 20:32:56 changed by patrick

  • status changed from new to closed.
  • resolution set to worksforme.

The VR Juggler 2.2 Beta 1 build does not know about the new toolset naming convention in Boost 1.34.x, so the automatic detection of Boost libraries fails. This has already been fixed in the trunk and on the 2.2 branch and will be working correctly in the next release.

04/15/08 14:50:51 changed by renePurdue

  • status changed from closed to reopened.
  • resolution deleted.

I am encountering this same error message while building on F7 x_64 with boost 1_35 via "make optim".

My configure is (we build several concurrent versions): 

../configure.pl --with-boost=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps// --with-boost-includes=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps//include/boost-1_35/ --with-boost-fs-lib=boost_filesystem-gcc-mt-1_35 --with-cppunit=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps --with-cppdom=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps// --with-gmtl=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps// --prefix=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64 --with-java-orb=JDK --enable-openal=yes --with-jdkhome=/usr/java/latest/ --with-python-orb-lib=/usr/lib/python2.5/site-packages --with-python=/usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps//lib --with-alut=/usr

And the error snipit is: 

checking for backtrace... yes
checking for boost::filesystem::exists() in boost_filesystem-gcc-mt-1_35 in /usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps///lib64... no
checking for boost::filesystem::exists() in boost_filesystem-gcc-mt-1_35 in /usr/local/apps/vrjuggler-2.2-2008-04-01-linux-f7-amd64-deps///lib... no
configure: error: *** Boost.Filesystem required by VPR ***
make[2]: *** [Makefile] Error 1
make[1]: *** [recursive] Error 1
make: *** [optim] Error 2

I have tried the process on a the 2.2 branch and the trunk with similar results. I have also tried altering the —with-boost-fs-lib value to 1) resemble the name of the library 2) auto-detect (i.e. leave it unset) 3) to the value stated in the original ticket. All receive the same results.

Is there something I'm missing?

Thanks! Rene'

04/15/08 16:08:27 changed by patrick

  • owner set to patrick.
  • status changed from reopened to new.

I will look into this as soon as I can (tonight at the earliest).

04/16/08 10:44:10 changed by patrick

  • status changed from new to closed.
  • resolution set to fixed.

The problem with detecting Boost 1.35 libraries is fixed on the 2.2 branch with r21069 and on the trunk with r21067. The Windows build still needs to be updated, but the case there should be very quick to fix.

Add/Change #41 (config.pl exits with boost error - boost::filesystem::exists())




Change Properties
Action