On Sat, Dec 4, 2010 at 9:47 PM, Fabian Pedregosa <[email protected]>wrote:
> On Sat, Dec 4, 2010 at 10:29 AM, Gael Varoquaux > <[email protected]> wrote: > > On Sat, Dec 04, 2010 at 10:25:52AM +0100, Fabian Pedregosa wrote: > >> The correct command is "sudo gcc_select mp-gcc45" which effectively > >> does all the symbolic links for you and works like a charm, so please > >> ignore my previous patch. > > > > I am not a mac user, so I guess that my opinion is not very educated, but > > isn't your patch still useful: test if 'gcc' exists, and if not fallback > > to your patch, so that it still works for the clueless user? > > Indeed, having scipy build out of the box would be nice, but it's not > for me to decide if numpy.distutils should overcome these limitations > in macports ... > I would prefer to just document the gcc_select solution, since it solves the problem at hand. > > On the other hand, as installing on macports is not that trivial, I > strongly feel that a subsection 'Macports' should be added to scipy's > INSTALL.txt file, where it details needed packages, the gcc_select > trick and options needed in site.cfg for umfpack. I'll gladly provide > a patch for that if people are OK. > The most up-to-date instructions are at http://www.scipy.org/Installing_SciPy/Mac_OS_X, so those should be updated as well. That said, if a "Macports" section is added there should be a strong disclaimer that it is *not* the recommended way to install numpy/scipy. A good portion of the build problems reported on these lists are related to Fortran on OS X, and a specific gfortran build at http://r.research.att.com/tools/ is recommended for a reason. If a user really wants to use Macports some notes in the docs may help, but let's not give the impression that it's a good/default option for a new user. Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
