On 9 March 2011 16:53, Jan Raasch <jan.raa...@googlemail.com> wrote: > Thank you, Bill, you are right. After having a closer look at the > mpir-1.2.2.p2.spkg file I found that there is a function inside the > spkg-install file called > > remove_pic_osx_32_bit() > > which does exactly what you suggested (It deletes the asm files that > have the problem). Here is the part of the code of the spkg-install > file that decides whether or not the remove_pic_osx_32_bit() function > is run: > > ********************************************************************** > Darwin) > if [ "$SAGE64" = "yes" ]; then > echo "Building 64 bit OS X version" > ABI=64 > else > # Do not set ABI=32 on OS X 10.6, since there everything > # defaults to 64-bit. > if [ `uname -r | sed 's/\..*//'` != "10" ]; then > ABI=32 > if [ "`uname -m`" = "i386" ]; then > remove_pic_osx_32_bit > fi > fi > fi;; > ********************************************************************** > > So the problem was that, because I am running OS X 10.6 "uname -r" > provided a value of "10.*.*". So the remove_pic_osx_32_bit function > was never triggered even though I needed it, since I am on a 32bit > (Intel Core Duo) processor. > > I guess I am in the minority here, running OS X 10.6 on a 32bit > processor. If I am not mistaken, only the first generation MacBooks > and iMacs (Intel-based) run on the (32bit) Intel Core Duo. > > Cheers, > Jan
You may be in a minority, but it is still a bug. Is there a good way to determine if the system is 32-bit? On Solaris I could use 'isainfo -b', but that's not a POSIX command, so will not be portable. I expect there's something similar on OS X. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
