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

Make "ratpoints" check whether -fnested-functions is supported by the compiler #12368

Closed
jdemeyer opened this issue Jan 27, 2012 · 10 comments
Closed

Comments

@jdemeyer
Copy link
Contributor

On Darwin, ratpoints adds -fnested-functions (an Apple extension) to $CFLAGS causing failures when using gcc to compile.

spkg: http://boxen.math.washington.edu/home/jdemeyer/spkg/ratpoints-2.1.3.p2.spkg

Depends on #12367

Component: packages: standard

Author: Jeroen Demeyer

Reviewer: R. Andrew Ohana

Merged: sage-5.0.beta5

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

@jdemeyer

This comment has been minimized.

@ohanar
Copy link
Member

ohanar commented Feb 10, 2012

comment:2

shouldn't you append testflags.sh -fnested-functions to CCFLAGS?

@williamstein
Copy link
Contributor

comment:3

Replying to @ohanar:

shouldn't you append testflags.sh -fnested-functions to CCFLAGS?

I'm not sure. However, if he did then he would be changing how the spkg-install scripts works from before. It did not used to append to CCFLAGS -- it always wrote it from scratch. So I think appending or not is orthogonal to refereeing this patch; it could be another ticket.

My question is: what the heck is testcflags.sh? It doesn't exist on my OS X 10.7 install, or in Sage-5.0x as far as I can tell, or in this spkg... So I can't referee this package.

@jdemeyer
Copy link
Contributor Author

comment:4

Replying to @williamstein:

My question is: what the heck is testcflags.sh?

See #12367 (a dependency of this ticket).

It doesn't exist on my OS X 10.7 install

Did you look in $SAGE_ROOT/spkg/bin?

@jdemeyer
Copy link
Contributor Author

Diff for the ratpoints spkg, for review only

@jdemeyer
Copy link
Contributor Author

comment:5

Attachment: ratpoints-2.1.3.p1-p2.diff.gz

Replying to @williamstein:

I'm not sure. However, if he did then he would be changing how the spkg-install scripts works from before. It did not used to append to CCFLAGS -- it always wrote it from scratch.

I agree with R. Andrew, so I'm copying $CFLAGS to $CCFLAGS in spkg-install. Needs review.

@ohanar
Copy link
Member

ohanar commented Feb 13, 2012

Reviewer: R. Andrew Ohana

@ohanar
Copy link
Member

ohanar commented Feb 13, 2012

comment:6

Replying to @williamstein:

So I think appending or not is orthogonal to refereeing this patch; it could be another ticket.

Note that I did not mark it as needs work, I definitely agree that it is not necessary for refereeing this ticket. I would have given it a positive review regardless (since it did what it was supposed to do), but since it is a trivial change that improves the build process, and since he was already touching the CCFLAGS variable, I figured it couldn't hurt to actually have the global CFLAGS respected.

@williamstein
Copy link
Contributor

comment:7

Replying to @jdemeyer:

Replying to @williamstein:

My question is: what the heck is testcflags.sh?

See #12367 (a dependency of this ticket).

It doesn't exist on my OS X 10.7 install

Did you look in $SAGE_ROOT/spkg/bin?

Yes, but I guess sage-5.0.beta2 is too old. I'll let somebody else referee this:

deep:~ wstein$ cd s/spkg/bin/
deep:bin wstein$ ls
json_bundle.py	sage-env	testcc.sh	text-collapse
sage		sage-spkg	testcxx.sh	text-expand
deep:bin wstein$ sage -version
Sage Version 5.0.beta2, Release Date: 2012-02-03

@jdemeyer
Copy link
Contributor Author

Merged: sage-5.0.beta5

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