-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
add persistent SAGE64 building switch on OSX and Solaris #22
Comments
comment:1
|
comment:3
|
comment:7
Fixed in #1261 (PBuild) |
Attachment: trac_22.patch.gz |
comment:11
Mhh, looking at the complete ticket history this patch does not cover all what needs to be fixed on this ticket. I will post a patch on top that also fixes this issue. Cheers, Michael |
comment:12
Unfortunately the trick William suggested does not work everywhere, i.e. even on the latest stable Debian release this happens:
From man uname on that box:
So we might want to make that part of the ticket a followup ticket. Cheers, Michael |
comment:13
Having thought about this and played around a little with uname it seems that it will not work and is not fine grained enough anyway. I would suggest to do write a small C program that identifies the following:
The way we can properly identify the build platform and decide more intelligently if we issue a warning, i.e running the Fedora 10 build on a Fedora 9 box should abort since it doesn't work. The test should be wrapped in a shell script since the binary will obviously only run on a subset of arches, i.e. if the binary fails to run we just about and print a canned warning together with a config info saved as text that is created when building the binary. This is enough a task to split it off to a new ticket. I have some basic code that does some of the above already for OSX since I need this kind of code while cleaning up the build system. Thoughts? Cheers, Michael |
comment:14
This is a "perfect patch." ... ;-) |
comment:15
Merged in Sage 3.3.alpha1. Note that the remaining issue from this ticket has been moved to #5062. Cheers, Michael |
Should there be something to keep people from building on 32-bit then 64-bit then 32-bit.
Component: build
Issue created by migration from https://trac.sagemath.org/ticket/22
The text was updated successfully, but these errors were encountered: