Cool.
I have to build the OS X 10.4 versions of Sage 4.3.1 right now, but
will have a look at that one. Thanks!
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 o
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 wrote:
> > Is there a way to
> 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 work
