#13157: %fortran in the notebook (and fortran.eval on command line) is STILL 
broken
on OS X
----------------------------------+-----------------------------------------
       Reporter:  benjaminfjones  |         Owner:  was     
           Type:  defect          |        Status:  new     
       Priority:  major           |     Milestone:  sage-5.2
      Component:  interfaces      |    Resolution:          
       Keywords:  fortran osx     |   Work issues:          
Report Upstream:  N/A             |     Reviewers:          
        Authors:                  |     Merged in:          
   Dependencies:                  |      Stopgaps:          
----------------------------------+-----------------------------------------

Comment (by kcrisman):

 Umm, there is something really odd here.  The flags passed seem to
 indicate something went quite wrong.  For instance, one bit is
 {{{
 
/var/folders/f4/881mfg491yxdf3zx37ynf5580000gn/T/tmpSLdvBd/Users/bael/.sage/temp/Baels_MacBook_Air.local/2689/tmp_0.o
 -LUsing built-in specs. COLLECT_GCC=gfortran
 COLLECT_LTO_WRAPPER=/Users/bael/sage/sage-5.0.1/local/bin/../libexec/gcc/x86_64
 -apple-darwin10.8.0/4.6.3/lto-wrapper
 /Users/bael/sage/sage-5.0.1/local/bin/../lib/gcc/x86_64-apple-
 darwin10.8.0/4.6.3 -l gfortran -o ./fortran_module_0.so -l gfortran
 -shared-libgcc
 }}}
 What the heck?
 {{{
 -LUsing built-in specs. COLLECT_GCC=gfortran
 }}}
 No wonder the errors look like
 {{{
 gfortran: error: built-in: No such file or directory
 gfortran: error: specs.: No such file or directory
 gfortran: error: COLLECT_GCC=gfortran: No such file or directory
 }}}
 I don't know how that verbiage got passed there, though.

 Anyway, since
 {{{
 /Users/bael/sage/sage-5.0.1/local/bin/../lib/gcc/x86_64-apple-
 darwin10.8.0/4.6.3" -lgfortran -o ./fortran_module_0.so" failed with exit
 status 1
 }}}
 that means it's no surprise that at the end
 {{{
     os.unlink(name + '.so')
 OSError: [Errno 2] No such file or directory: 'fortran_module_0.so'
 }}}
 though that is just a symptom.

 Does ticket:8010:attachment:trac-8010_numpy.patch (sorry, can't get the
 link right) look like it might solve it for you, just on the off chance?
 One would have to make a new spkg, of course.  But the patch was never
 applied, to my knowledge.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13157#comment:1>
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.

Reply via email to