On Wed, 15 Oct 2014, Kameeko Kiwi wrote: > Ultimately I'm trying to find a way to point Libmesh to a particular > version of Boost. There seems to be one (v1.46) in "/usr/include" that > perhaps came with the operating system; the new one that I installed > (v1.55, via "apt-get install libboost-dev") and want to work with put > itself in "/usr/local/include". When I run
> " > ./configure --prefix=/home/kameeko/software/libmesh_build4 > --enable-everything --enable-petsc --enable-mpi > PETSC_DIR=/home/kameeko/software/petsc PETSC_ARCH=arch-linux2-c-debug > --enable-boost BOOST_CPPFLAGS="-I/usr/local/include" > BOOST_LDFLAGS="-L/usr/local/lib64" > " > > the config.log shows > > " > BOOST_CPPFLAGS='-I/usr/include/' > BOOST_LDFLAGS='-L/usr/lib' > " > > so it doesn't seem to be acknowledging the newer Boost version... You can try configuring --with-boost= or setting $BOOST_DIR, but in your case that's still very risky. Even after libMesh detects the desired version of boost, you're almost certain to end up with /usr/include and /usr/lib in your include and library paths due to other system-provided dependencies. With boost things *might* still work, since IIRC they're very rigorous about keeping version numbers in include file subdirectory names and library name suffixes; but with just about any other library we use, having two different versions in your paths is a recipe for disaster, and the only safe way to juggle multiple versions is to keep them all out of common paths like /usr. --- Roy ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
