On Mon, Feb 12, 2018 at 12:43 PM, Victor Eijkhout <eijkh...@tacc.utexas.edu>

> I’m attaching a configure log file. I put a python library in the LIBS
> variable, and it is found and validated, but then not added to the optional
> libraries. This means that during linking I get an error from pytrilinos
> which can not find the python library.

It doesn't look like we do anything with $LIBS during configure, other than
to use it for test linking.

As a short term workaround, you could try putting your custom library+path
in the $libmesh_LDFLAGS environment variable, as I think we actually
respect the value of that one.

I think to be consistent with libmesh_LDFLAGS and libmesh_CXXFLAGS, we
would probably end up reading the value of libmesh_LIBS from the
environment. This is definitely non-standard, but I think the thinking was
to avoid accidentally picking up LDFLAGS/CXXFLAGS/LIBS from the user's
environment that they may have set for other reasons...

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Libmesh-users mailing list

Reply via email to