With MOOSE we're set up to use either the in-tree build (ie no build directory) or the an installed libMesh (after "make install"). I've never tried to use the build directory directly (did you point LIBMESH_DIR at your build directory?).
BTW - last time I tried yesterday, in-tree builds are still broken in libMesh because of the new Exodus stuff (unless it's been fixed lately!). Derek Sent from my iPad On Feb 8, 2013, at 10:37 AM, Jed Brown <j...@59a2.org> wrote: > $ ~/src/libmesh/build-petsc33-mpich/contrib/bin/libmesh-config --include > -I/usr/local/include -I/usr/include -I/usr/include/eigen3 > -I/home/jed/petsc-3.3/include -I/home/jed/petsc-3.3/mpich/include > -I/opt/mpich/include > > > It seems to me that this needs to include > -I/home/jed/src/libmesh/build-petsc33-mpich/include (and perhaps > .../include/libmesh). It doesn't help to use the install prefix before it is > "installed". > > I'm assuming that the library is supposed to be usable from the build > directory and that MOOSE's use of libmesh-config --include is supposed to be > sufficient. > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Libmesh-devel mailing list > Libmesh-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
