It turned out that there was another bug in there. At least on my machine, f2py was still broken on 4.3.1.rc1. I tracked down the problem (mac gcc doesn't support -shared) and there's a patch ready for review at ticket #8010.
Cheers, Felix On Jan 15, 10:42 am, gsw <georgswe...@googlemail.com> wrote: > > Is there a way to get sage to prefer /usr/bin/gcc to /usr/local/bin/ > > gcc that is easier than temporarily editing my path globally? Does > > Currently, adjusting the global path is the best way. > > > sage's fortran normally work on macs or has it been neglected over the > > Sage's fortran normally works, but OS X 10.6 gave us headaches, see > trac ticket #7095. Once Sage 4.3.1 is released, check it out again. On > the one hand, ticket #7095 most probably will be fixed --- on the > other hand, ticket #7860 indicates that there still might be another > open problem. > > > years? Any ideas how I could get it working? > > > Many thanks, > > Felix > > Cheers, > Georg
-- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
