-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
palp spkg ignores global CC and CFLAGS variables #7071
Comments
This comment has been minimized.
This comment has been minimized.
Author: R. Andrew Ohana |
Attachment: palp-1.1.p4.patch.gz for review purposes |
Work Issues: respect CFLAGS too |
comment:2
Can we pass CFLAGS, too? That will allow us to get rid of that horrible |
comment:3
Palp 2 is out and I have a preliminary spkg at #12055. Please base your work on the new version. |
comment:4
ok, I've based my changes off of the new version at #12055 and have made |
This comment has been minimized.
This comment has been minimized.
Dependencies: #12055 |
Attachment: palp-2.0.p1.patch.gz for review purposes |
Changed work issues from respect CFLAGS too to none |
comment:5
Looks good! |
Reviewer: Volker Braun |
Patch from #12055 needs to be applied |
comment:6
Attachment: trac-12055-SAGELOCAL_BIN.patch.gz I've switched the old ticket #12055 to invalid to not make Jeroen replace the spkg twice. But we still need the patch to the Sage library from there. |
This comment has been minimized.
This comment has been minimized.
comment:7
Replying to @orlitzky:
The "xyes" test, as it is called above, is the safest, most portable way to test for a string, as other methods, like the proposed change, can fail under obscure conditions. One might argue they don't fail with modern versions of bash, but IMHO is it worthwhile to write scripts which will always work under all conditions. The original code will always work - the proposed change is less portable. I suggest you take a look at the scripts created by autoconf. You will find they use a similar method to what was in Sage, as it is known to always work. As such, I believe the change is a retrograde step. Dave |
comment:9
I disagree. The xblah test makes it more difficult to read the test, which both increases the chance for errors as well as the long-term maintenance effort. A quick survey shows that at least half of the Sage spkgs use the simplified test, so clearly nobody has yet encountered a shell ancient enough to not work. I'm pretty sure many upstream sources use simplified tests, too, so there is basically no hope of ever compiling Sage on such a system without installing a shell that isn't from the middle ages. Autotools output really is a totally different issue, since their scripts are autogenerated readability is not an issue (and usually is pretty bad, in fact). If you disagree we can discuss this on the sage-devel, but its such a pervasive issue throughout Sage that it doesn't really matter if we use the simplified test in one spkg more or less. |
This comment has been minimized.
This comment has been minimized.
Merged: sage-5.0.beta7 |
Using
This is one of the many packages that ignore the setting of the variable CC.
To update:
Depends on #12055
CC: @orlitzky
Component: build
Author: R. Andrew Ohana
Reviewer: Volker Braun
Merged: sage-5.0.beta7
Issue created by migration from https://trac.sagemath.org/ticket/7071
The text was updated successfully, but these errors were encountered: