Hi Bernd,
On 03/05/15 20:11, Bernd Mohr wrote:
Kenneth,
Markus,
I finally tracked down the issues with /lib64 vs /lib.
[Note for others: On SuSE, when installing packages based on GNU
autotools, libraries often end up in <prefix>/lib64 instead of
<prefix>/lib like on other Linux variants. This often causes failures
in the sanity_check step with EasyBuild, which makes you angry at some
point if you had to re-install a package with a re-worked sanity check
the 10th time ;-) ]
It boils down to site-specific defaults as described in the GNU
autotools documentation (e.g. see
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Site-Defaults.html#Site-Defaults).
On SuSE, /etc/profile.d/site.sh sets
CONFIG_SITE="/usr/share/site/x86_64-unknown-linux-gnu"
(file attached), which changes libdir to /lib64 on 64-bit systems.
I confirmed the behavior: the next library installed with EasyBuild ended
up in /lib when I unsetted CONFIG_SITE and in /lib64, when I restored it
So as discussed last week, sanity_checks needs a 'library' key, where
one would specify only the name of the library and EasyBuild checks
whether it is in the right lib<whatever> dirctory (of course taking
CONFIG_SITE into account when installing autotools packages !)
Thank you very much for sharing this, this is indeed going to be very
useful when looking into support for extending the recognized keys in
the sanity check to 'libs' or 'libraries', or even 'shared_libs',
'static_libs'.
regards,
Kenneth
