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 README.txt to require Fortran as a pre-requisite for compiling Sage on Linux #7484
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Regarding this ticket:
|
comment:3
See #7485 |
Changed author from Jason Grout to Jason Grout, Minh Van Nguyen |
comment:4
Due to #7485, Linux Fortran binaries are now removed from the Fortran spkg. This means that under Linux, Fortran is a pre-requisite for compiling Sage from source just as the GCC suite of compilers is a pre-requisite. The new README.txt states that Fortran is a pre-requisite for compiling Sage on Linux. This file is based on that in Sage 4.3.1.rc1. The diff file README.diff shows differences between the attached README.txt and the one in Sage 4.3.1.rc1. Don't apply this diff file. Just replace the current README.txt under SAGE_ROOT with the attached README.txt. |
comment:5
I think it is important to add on platforms such as Solaris, AIX and HP-UX, where both 32 and 64-bit builds are supported, the library path must point to the 32-bit library if building 32-bit, and must point to a 64-bit library if building 64-bit. (How about OS X? Perhaps the fortran.spkg takes care of that.) On Solaris that will probably be the following, though this would need checking.
Dave |
Reviewer: David Kirkby |
comment:6
Do NOT require gfortran on OS X, since we still supply it with Sage. |
comment:7
William, you said on sage-devel, on the subject of SAGE_FORTRAN and OS X. *Use the binary included in Sage if SAGE_FORTRAN is not specified. Otherwise, use the one pointed to by the that environment variable. * http://groups.google.com/group/sage-devel/browse_thread/thread/e2867ea2efe7e052 Therefore, SAGE_FORTRAN_LIB might be important if someone wanted to use their own version of gcc, rather than the one in Sage. In which case, the question arises as to what would be the path to the library. Would it be different for 32 and 64-bit builds, as it is on Solaris and HP-UX? Dave |
comment:8
Ticket #8080 updates the Installation Guide to require gfortran as a pre-requisite for compiling Sage on Linux. |
comment:9
Replying to @sagetrac-drkirkby:
Done. Fixed in the updated README.txt.
Also fixed in the updated README.txt. For Mac OS X, I have removed the reference to ticket #7095, as the issue contained therein has been fixed. |
comment:10
README.txt also fixes #8106. |
Attachment: README.txt based on Sage 4.3.3.alpha0 |
based on Sage 4.3.3.alpha0 |
comment:11
Attachment: README.diff.gz A few comments: Those in bold are specifically about Fortran. The others are not, so you can ignore them for this ticket, tough you might chose to update them, as they are minor changes:
Dave |
comment:12
From IRC:
|
This comment has been minimized.
This comment has been minimized.
comment:14
README.txt was recently updated, so this will need to be rebased again. Is the original problem still a problem, given the latest one? With respect to drkirkby's comments, I think the following remain:
This seems reasonable to change.
I have no idea if this is true, but at any rate we still use the phrase "system-wide" in line 137.
These three seem to be a matter of taste. As long as we accurately document what Sage builds with, we might as well leave it alone. And warnings of things that fail are good if they prevent people from wasting time trying to make them fail :) |
comment:15
This has already been taken care of at least as of Sage 4.5.2. I'm going to mark it as invalid now. |
Here's a patch for README.txt to document this:
Ticket #8806 fixes many issues that are dealt with in the current ticket.
CC: @haraldschilly
Component: build
Author: Jason Grout, Minh Van Nguyen
Reviewer: David Kirkby
Issue created by migration from https://trac.sagemath.org/ticket/7484
The text was updated successfully, but these errors were encountered: