William Stein wrote: > > This code below *should* have been in sage-env, not every single > > spkg-install. If that had been the case, I doubt you would be so > > annoyed by it, since you could trivially just delete the Darwin part: > > > > if [ `uname` = "Darwin" -a $SAGE64="yes"] > > CFLAGS="$FLAGS -m64" > > CXXFLAGS="$CXXFLAGS -m64" > > fi > > > > Very true. > > It find it most annoying. Mainly since it only works on OS X, and > Micheal new of plans for a 64-bit Solaris port. He would have also known > the correct flag was -m64 on any compiler for any of the supported > platforms. > > > We could automate deleting those lines from every single spkg-install as > follows. > > (1) take the official sage-4.2.tar (say) release. > (2) write a script to unpack each spkg-install, delete those lines if > they occur, do "hg ci", then repack it. > (3) retest sage-4.2.tar everywhere. > (4) release. > > Bumping the version numbers doesn't really matter since that is only to > force upgrading, which isn't needed (or desired!) for this fix. > > William
I'll write a revised sage-env, and let you write the script. On a very rough guess, 75% of the libraries and binaries were built as 32-bit on a 64-bit Solaris build, so I suspect somewhere around 75% of the packages could be fixed in an automated fashion. That would still leave quite a few to do manually, but it is better than doing them all! 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 -~----------~----~----~----~------~----~------~--~---
