search

idaholab / moose

Multiphysics Object Oriented Simulation Environment
https://www.mooseframework.org
GNU Lesser General Public License v2.1
1.76k stars 1.05k forks source link

Don't rely on libmesh configuration when using conda #16232

Open lindsayad opened 3 years ago

lindsayad commented 3 years ago

Bug Description

The libtool that is shipped with libmesh in conda already has a path hard-coded for sed, corresponding to that of the machine on which the conda package is built. If that sed path doesn't correspond to the sed path on the platform on which we're building MOOSE (e.g. using conda libmesh), then we won't be able to link any libraries. We get an error like we see on #16123 like:

/usr/bin/sed: not found

Steps to Reproduce

The newest conda libmesh was built on meowbuild; previous conda libmesh packages had been built on our older boxes. It seems that meowbuild has sed at /usr/bin/sed whereas our older boxes use /bin/sed.

Impact

This is stopping @cticenhour development of Freya, so a huge impact for one of our developers, and we are getting repeated error reports from users on #16123. This seems fairly important.

lindsayad commented 3 years ago

Using system libtool isn’t the right answer...it’s not going to be configured with our shared/static library preferences.

lindsayad commented 3 years ago

I think we're going to end up doing more configure ourselves (e.g. with MOOSE). But we may do it with cmake instead of autotools.