There's a lot of code in Sage which has something like this in it:
if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then
# OS X 64-bit hacks on OS X
fi
In Numpy, there's a 64-bit hack which looks pretty alful to me.
# numpy's distutils is buggy and runs a conftest without
# taking CFLAGS into account. With 64 bit OSX this results
# in *boom*
if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then
echo "64 bit MacIntel: copying fake gcc"
rm $SAGE_LOCAL/bin/gcc
cp gcc_fake $SAGE_LOCAL/bin/gcc
chmod 755 $SAGE_LOCAL/bin/gcc
fi
then later this fake gcc gets deleted.
if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then
echo "64 bit MacIntel: deleting fake gcc"
rm $SAGE_LOCAL/bin/gcc
fi
I think a much simpler solution is just to set
CC="gcc -m64"
export CC
and that's it.
No messing around with fake gccs. But I'd like access to an OS X machine which
defaults to 32-bit, but can build 64-bit, in order that I can test this.
Dave
I have an Osx 10.5 intel Mac that I can get you remote access to,
which I think has the above property. This won't happen until I go
to CPUs though (Monday). Remind me!
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org