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
Update prereq to version 0.6 #7781
Comments
This comment has been minimized.
This comment has been minimized.
Attachment: testcc.sh.gz With correected comment about number of command line arguments. |
comment:2
Ignore testcc.sh - I attached it to the wrong ticket! Dave |
comment:3
In the file
could be replaced with
From line 356 onward, the following section appears twice:
|
comment:4
Thank you for your comments.
I'll make those changes. Dave |
comment:5
I made those changes, and a few more where the tests could be made sightly more robust. They probably make no practical difference, but a good habit to get into. dave |
Reviewer: Minh Van Nguyen |
comment:7
As of Sage 4.3, some files are not propertly under revision control:
The release manager needs to first do the following:
After going through the above steps, then get http://boxen.math.washington.edu/home/kirkby/portability/prereq-0.6/prereq-0.6-install put it under http://boxen.math.washington.edu/home/kirkby/portability/prereq-0.6/prereq-0.6.tar and put it under
This is expected, as AIX is not yet supported. As expected, a message would be printed warning about AIX being an unsupported platform. To get pass the message, one could set the SAGE_PORT=yes and then issue "make".
This is expected, as Sage is not supported on Cygwin. As expected, a message would be printed warning about Cygwin being an unsupported platform. To get pass the message, one could set the SAGE_PORT=yes and then issue "make".
This is expected. I think one can build cliquer by some suitable editing of that spkg's file spkg-install. As of Sage 4.3, only Linux, Mac OS X, and Solaris are supported by that installation script. As expected, a message would be printed warning about HP-UX being an unsupported platform. To get pass the message, one could set the SAGE_PORT=yes and then issue "make".
This is expected as x86 Solaris is not yet supported. As expected, a message would be printed warning about non-SPARC Solaris being an unsupported platform. To get pass the message, one could set the SAGE_PORT=yes and then issue "make".
For the above test platforms, the updated prereq package works as advertised. |
comment:8
I've fixed the issues with the base/ repo in 4.3.1.alpha0. |
comment:9
Just note, http://boxen.math.washington.edu/home/kirkby/portability/prereq-0.6/prereq-0.6-install will need execute permissions, as its a shell script. If you download via the web, it will probably lose them. |
Merged: sage-4.3.1.rc0 |
comment:10
Very carefully followed all instructions to the letter! |
Changed merged from sage-4.3.1.rc0 to none |
Merged: sage-4.3.1.rc0 |
comment:12
Sorry! |
This is a further update of the code which checks the prerequisites for Sage are OK. Previous updates were #7021 and #7352.
== Changes in files ==
Changes to configure.ac (This gets included in prereq-0.6.tar)
As in prereq 0.4 and 0.5, the Sage build exits with gcc < 3.4.0 (as it's too old) and with gcc 4.0.0 (as it's too buggy). The previous release gave a warning for gcc 3.4.x, but did not exit. This was unsatisfactory, as on a fast Solaris machine, the warning is likely to be missed.
Changes to prereq-0.6-install
Updated versions of prereq-0.6-install and prereq-0.6.tar are provided in the directory below. prereq-0.6-install must be put into Sage with execute permissions.
http://boxen.math.washington.edu/home/kirkby/portability/prereq-0.6/
== How to test these changes ==
Anyone wishing to test on HP-UX is welcome to have an account on my own machine.
CC: @mwhansen @sagetrac-GeorgSWeber @sagetrac-mvngu
Component: build
Keywords: gcc AIX HP-UX IRIX Tru64 Solaris
Author: David Kirkby
Reviewer: Minh Van Nguyen
Merged: sage-4.3.1.rc0
Issue created by migration from https://trac.sagemath.org/ticket/7781
The text was updated successfully, but these errors were encountered: