Believe it or not, mpi has been standard on mac for several years and is
pretty solid. I'm with you on the bug reporter. Here's the address (and for
those that don't know it, ADC membership is free so anybody can submit a bug
report):
https://bugreport.apple.com
On Wed, Jun 2, 2010 at 12:44 AM,
On Wed, Jun 2, 2010 at 1:41 AM, Chris Kees wrote:
> Hey, thanks, that patch fixed it. Yes, I'm on a 64-bit mac. We've had a lot
> of trouble with numpy distutils and fortran on the mac unrelated to sage. I
> was hoping that sage would provide a way to avoid those hassles among other
> things. App
Hey, thanks, that patch fixed it. Yes, I'm on a 64-bit mac. We've had a lot
of trouble with numpy distutils and fortran on the mac unrelated to sage. I
was hoping that sage would provide a way to avoid those hassles among other
things. Apple could make life a hell of a lot easier by including
gfor
Hi Chris,
Are you on a 64-bit mac, i.e. core 2 duo or newer? I believe Sage's
implementation of f2py is broken on 64-bit macs - certainly it is
broken on mine too.
There is a simple patch that fixes this problem at
http://trac.sagemath.org/sage_trac/ticket/8010 , if anyone wants to
review it.
U
On 1 June, 14:45, Chris Kees wrote:
> Hi,
>
> I'm trying to build a fortran extension module with f2py using and spkg I've
> built for sage 4.4.2 on Mac OS X 10.6. When I just run 'python setup.py
> install' from the commandline (with SAGE_LOCAL at the front of my path,
> etc.) The module build/
