-
Notifications
You must be signed in to change notification settings - Fork 160
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
Improve buildsystem by exporting GMP_PREFIX
in sysinfo.gap
for package build systems
#5079
Conversation
GMP_PREFIX
in sysinfo.gap
for package build systems
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR looks generally sensible to me. I like that it documents the circumstance under which GMP_PREFIX will be empty. I'm not exactly sure what should happen under the "make install" situation (it seems possible that there may be some unforeseen consequences). Since "make install" is not yet a going concern, this seems academic for now.
Not sure what you mean (EDIT: as in: I am not sure how to interpret the above, which certainly is my fault; I'll try my best to interpret it and give answers to my guesses what you may have meant, sorry if I guessed wrong) -- as documented, the version of Or perhaps you were wondering if there are other values |
Demo PR for nq to use this: gap-packages/nq#24 |
If nobody minds (@ChrisJefferson ?) I'd like to backport this for 4.12.1 -- while it's not strictly a bugfix, it's a minor thing that'll be useful for packages and users, and the sooner we get it into a release, the sooner it can have a beneficial effect. At the same time, I don't see how it could have any negative impact anywhere (of course that's far from meaning there is no opportunity for that happening... but at least I made sure to check that no package uses a variable named |
looks good to me |
Backported to stable-4.12 via commit 6a63779 |
Resolves #5072