#9368: sage_fortran ignores SAGE64 except on Solaris/OpenSolaris
--------------------------+-------------------------------------------------
Reporter: drkirkby | Owner: GeorgSWeber
Type: defect | Status: closed
Priority: critical | Milestone: sage-4.5
Component: build | Resolution: fixed
Keywords: | Author: David Kirkby, William Stein
Upstream: N/A | Reviewer: Robert Miller
Merged: sage-4.5.rc2 | Work_issues:
--------------------------+-------------------------------------------------
Comment(by drkirkby):
Replying to [comment:14 was]:
> OK, I've found the problem. The build script is written in Python.
Thus the fortran spkg *depends* on Python. However, for me, when I built
the fortran spkg, it got built before Python, hence some random system-
wide wrong python was used, and this broke the build. This was a problem
that could have happened on many different systems in weird ways, so it's
very good that Robert Miller and I persisted and tracked this down,
instead of brushing it off.
I'm afraid to say I don't share your confidence that you and Robert have
tracked this down completely, though you have found a serious flaw.
Clearly adding this dependency to {{{$SAGE_ROOT/spkg/standard/deps}}} is
correct - the fortran package uses Python, so Python must be built first.
I'm not arguing with that.
However, I'm not convinced this was William's problem, as the
{{{$SAGE_LOCAL/bin/sage_fortain}}} script '''must''' have been working at
one point, otherwise ATLAS, Linpack, Numpy and other things that used
Fortran would not have built. As I posted on sage-release, William's
{{{install.log}}} had in it
{{{
sage_fortran -fPIC -c lsame.f -o lsame.o
sage_fortran -fPIC -c lsametst.f -o lsametst.o
sage_fortran -o testlsame lsame.o lsametst.o
sage_fortran -fPIC -c slamch.f -o slamch.o
sage_fortran -fPIC -c slamchtst.f -o slamchtst.o
sage_fortran -o testslamch slamch.o lsame.o slamchtst.o
}}}
However, when I looked at William's $SAGE_LOCAL/bin/sage_fortran, it had
only:
{{{
#!/bin/sh
}}}
in it. There is '''no way''' that could have been used to compile ATLAS,
Linbox, Numpy etc, all of which had built successfully.
Hence I believe that something other than the fortran package later
modified {{{$SAGE_LOCAL/bin/sage_fortran}}}. Unless I'm mistaken, the bug
does not reside in the fortran package at all, but rather in something
that was built after ATLAS, Numpy and Linbox.
Comments?
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9368#comment:18>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
