Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maybe remove linking xpm into gd #7162

Closed
williamstein opened this issue Oct 8, 2009 · 8 comments
Closed

maybe remove linking xpm into gd #7162

williamstein opened this issue Oct 8, 2009 · 8 comments

Comments

@williamstein
Copy link
Contributor

I'm trying to build sage-4.1.2 on disk.math.washington.edu (opensolaris x86) and had to change the spkg-install of gd-2.0.35.p2:

# We explicitly disable X support, since (1) X is not a SAGE dependency,
# and (2) the gd build fails on a lot of OS X PPC machines when X is enabled.
./configure --prefix="$SAGE_LOCAL" --without-jpeg --without-x --without-xpm --with-zlib="$SAGE_LOCAL" --with-freetype="$SAGE_LOCAL"

I added --without-xpm.

Maybe we should make this standard?

CC: @williamstein @sagetrac-drkirkby @jaapspies

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/7162

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Nov 4, 2009

comment:1

It seems sensible to make it standard to me.

If you want to post a package, I'll review it.

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Jan 2, 2010

Author: David Kirkby

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Jan 2, 2010

comment:2

Attachment: 7162.patch.gz

A revised .spkg can be found at

http://boxen.math.washington.edu/home/kirkby/portability/gd-2.0.35.p3/gd-2.0.35.p3.spkg

@jaapspies
Copy link
Member

comment:3

Replying to @sagetrac-drkirkby:

A revised .spkg can be found at

http://boxen.math.washington.edu/home/kirkby/portability/gd-2.0.35.p3/gd-2.0.35.p3.spkg

This change make the build depend on setting export CFLAGS=-m64

Is this a good thing to do?

Jaap

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Jan 2, 2010

comment:4

Hi,
you have a point, but there was some logic to this.

The purpose of the ticket which William opened was to add

--without-xpm

to the line where the configure script it invoked. The ticket had nothing to to with SAGE64.

I think whilst trying to build on Solaris in 64-bit mode, you should set CFLAGS and CXXFLAGS to include -m64, as that will allow some packages to build without making changes to their spkg-install files. This is one such package.

I've written two scripts (#7505) which check what the compiler is (GCC, Sun Studio, HP, IBM etc). That ticket already has positive review.

I've written an updated version of sage-env, #7818 which is awaiting review. That will uses those two script, determine the right compiler flag, then automatically export the right compiler flag to CFLAGS.

As such, I believe making only the change William suggested is sufficient in this case. Just export CFLAGS and CXXFLAGS to include -m64, and expect that in the next release or two, that will happen automatically for you. Doing this, will reduce somewhat the number of spkg-install files that need editing.

Dave

@jaapspies
Copy link
Member

Reviewer: Jaap Spies

@jaapspies
Copy link
Member

comment:6

Ok, nobody is hurt here. People who are porting should know this.

So I give it a positive review.

Jaap

@mwhansen
Copy link
Contributor

mwhansen commented Jan 3, 2010

Merged: sage-4.3.1.alpha0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants