Open yurivict opened 6 years ago
@yurivict the MOOSE build system uses the libtool provided by libmesh. Ith is selected here:
https://github.com/idaholab/moose/blob/devel/framework/build.mk#L45-L51
If your build process looks in /usr/local/libtool
something must have gone wrong. E.g. LIBMESH_DIR
is set to /usr/local
maybe?!
If your build process looks in /usr/local/libtool something must have gone wrong.
I am on FreeBSD. It's just not allowed to install anything directly under $PREFIX, or into other random places. This is why I removed libtool installed by libmesh in the FreeBSD port that I created. On the other hand, there is the standalone libtool package that works fine. MOOSE shouldn't use something that libmesh installs improperly. You should still rely on/require standalone libtool.
MOOSE shouldn't use something that libmesh installs improperly. You should still rely on/require standalone libtool.
To date, we've had little reason to create an independent configure process for MOOSE as our project completely piggybacks on the successful installation of libMesh. That may change in the future, but the fix if needed here should really go into libMesh and then we'll just pick it up.
I think @yurivict is interested in building a FreeBSD package for bhallalab/moose. Unlike us, they package their code. So, if my assumption is correct, we can just close this issue...
I am creating FreeBSD packages for both MOOSes. I'm done with bhallalab one. Still figuring out yours, exactly because it doesn't provide the installation procedure and relies on non-standard things from libMesh that can't be accepted on FreeBSD.
libtool is installed in /usr/local/bin/libtool, and is in the path.