Displaying 3 results from an estimated 3 matches for "nodeflib".
Did you mean:
nodefile
2019 Apr 08
1
selftest, help with a single test
...be caused by them being in /usr/lib64 instead of
> /usr/lib or what else
This is in fact what was making this test fail: after fixing the path in
config_cache.py, it run like a charm.
Thanks for the hint!
BTW the loader doesn't like LD_PRELOAD without a full path for
executables with -z nodeflib or run in secure-execution mode. I don't
know if any of these apply to the test.
2019 Apr 07
1
selftest, help with a single test
Hi,
Yes, you're right, the problems are due to the selftest environment
failing to start up. In this case, you could just reproduce the same
problem with:
SELFTEST_TESTENV=s4member:local make testenv
There may be some package dependencies you're missing in order to get
selftest to run correctly. In a earlier message it looked like you were
missing the python DNS package (python-dnspython
2007 May 13
1
Help understanding LAPACK symbol resolution
R developers,
I am trying to understand how symbols are resolved, so that I can
configure a package that I contributed to, and so that I can provide
guidance to (linux / OSX) users of the package. To be concrete, my
package uses the LAPACK Fortran symbol zsysv. This is not in
libRlapack, but is defined on my system in the library
/usr/lib64/liblapack.so.
* I suspect that the reason the symbol is