freetype always builds 32-bit libraries on Solaris, even when SAGE64="yes"

[sagetrac-drkirkby]

Using

• A Sun Blade 2000 running Solaris 10 update 7
• Sage 4.1.2.rc0
• gcc 4.4.1
• SAGE64 exported to "yes"

Looking at the directory $SAGE_HOME/local/lib, we can see the freetype libraries are 32-bit, even though SAGE64 was set to "yes"

drkirkby@swan:[~/sage/gcc64-sage-4.1.2.rc0/local/lib] $ file libfreetype*
libfreetype.a:  current ar archive, not a dynamic executable or shared object
libfreetype.la: commands text
libfreetype.so: ELF 32-bit MSB dynamic lib SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped
libfreetype.so.6:       ELF 32-bit MSB dynamic lib SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped
libfreetype.so.6.3.16:  ELF 32-bit MSB dynamic lib SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped

This is far from the only package building 32-bit when SAGE64 is set to "yes" on Solaris. All of the following do, and I suspect there are many others too.

• zlib zlib-1.2.3.p4 always builds 32-bit binaries on Solaris. #7128
• libgpg_error libgpg_error-1.6.p2 always builds 32-bit binaries on Solaris. #7129
• libpng libpng 1.2.35 always builds 32-bit libraries on Solaris. #7130
• libcliquer libcliquer always builds 32-bit libraries on Solaris. #7131
• pari pari-2.3.3 always builds 32-bit libraries on Solaris. #7133
• ntl ntl 5.4.2.p9 always builds 32-bit libraries on Solaris. #7134
• python python always building 32-bit on Solaris #7135
• gp gp always building 32-bit on Solaris #7136
• ratpoints ratpoints always building 32-bit on Solaris even when SAGE64="yes" #7137

mpir currently mixes 32 and 64-bit objects, so does not build at all #7132.

I will sort this package out after creating a new sage-env, which exports all the variables properly, including the flag for building 64-bit code, which is not always -m64.

Although there is no support for AIX or HP-UX in Sage yet, we could potentially add it - I personally own machines running AIX and HP-UX.

IBM's compiler on AIX uses -q64, and HP's on HP-UX uses +DD64.

The sensible way to resolve this is to add the correct flag on every platform. This is not a very difficult task really. Whilst any changes to the source that might be necessary for a port would take a lot of time, finding the right flags to build with should be quite easy.

Component: porting: Solaris

Author: David Kirkby

Reviewer: Jaap Spies

Merged: sage-4.3.1.alpha0

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

[sagetrac-drkirkby]

comment:3

I decided to make only the minimum changes necessary to get this to build 64-bit with gcc. As such, the only change is to spkg-install, so instead of -m64 being added only on Darwin, it is now added whenever SAGE64 is set to yes.

I'll leave a better fix until a later date. See

http://boxen.math.washington.edu/home/kirkby/portability/freetype-2.3.5.p2/

[sagetrac-drkirkby]

Author: David Kirkby

[jaapspies]

comment:5

Looks ok for me. Tested on Open Solaris 0906 64 bit and Fedora 12.

I think SPKG.txt needs work, that can be done later by the official maintainer :)

Positive review.

Jaap

[jaapspies]

Reviewer: Jaap Spies

[sagetrac-drkirkby]

comment:6

I think you mean spkg-install needs further work, not SPKG.txt

But this will at least allow it to build with gcc on Open Solaris.

[jaapspies]

comment:7

Replying to @sagetrac-drkirkby:

I think you mean spkg-install needs further work, not SPKG.txt

But this will at least allow it to build with gcc on Open Solaris.

I really mean SPKG.txt as it is not conform the rules!

William is the maintainer so he will make the changes sometime.

spkg-install is ok withe me.

Jaap

[mwhansen]

Merged: sage-4.3.1.alpha0