slackware-14.2 multilib: Building iml fails

[mkoeppe]

From https://groups.google.com/d/msg/sage-devel/WshDn3e_l3k/YInQI_-WAwAJ:

the real issue is that when building iml the libraries are hardcoded to reside at /lib, but in multilib systems this may not be the case. Specifically, in Slackware (see #29798 for slackware-multilib) we have lib for 32-bit and lib64 for 64-bit. I fixed this by changing this line in build/pkgs/iml/spkg-install.in:

SAGE_GMP_LIB="echo "$SAGE_GMP_INCLUDE" | sed 's|/include|/lib|'"

to this:

SAGE_GMP_LIB="echo "$SAGE_GMP_INCLUDE" | sed 's|/include|/lib{$LIBDIRSUFFIX}|'"

where LIBDIRSUFFIX is specified by our build to be null for 32-bit or 64 for 64-bit.

CC: @orlitzky @dimpase

Component: porting

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/29795

[mkoeppe]

comment:2

Indeed this code from build/pkgs/iml/spkg-install.in needs improving...

# When using GMP from a standard system location it shouldn't really
# matter what we put here, but iml's configure script requires we
# provide *something*, and this should be reasonable in most cases
SAGE_GMP_LIB="`echo "$SAGE_GMP_INCLUDE" | sed 's|/include|/lib|'`"

[orlitzky]

comment:4

Upstream IML should be smarter about detecting GMP, it just guesses at /usr/local/lib and /usr/lib by default.

To that end: it would be nice if the pkg-config file for gmp included the -L/usr/libX flag needed to link against it in the "Libs" field. But in the meantime we can probably fake it with...

$ pkg-config --variable=libdir gmp
/usr/lib64

[mkoeppe]

comment:6

Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.

[mkoeppe]

comment:10

outdated

[dimpase]

Reviewer: Dima Pasechnik