Opened 13 months ago

Last modified 3 months ago

#29795 new defect

slackware-14.2 multilib: Building iml fails

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.4
Component: porting Keywords:
Cc: mjo, dimpase Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by 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.

Change History (6)

comment:1 Changed 13 months ago by mkoeppe

  • Cc mjo dimpase added

comment:2 Changed 13 months ago by mkoeppe

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|'`"

comment:3 Changed 13 months ago by mkoeppe

  • Description modified (diff)

comment:4 Changed 13 months ago by mjo

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

comment:5 Changed 8 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:6 Changed 3 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

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.

Note: See TracTickets for help on using tickets.