In order that a package build fully under Solaris, under all reasonable circumstances, there are 8 possibilities that need to be considered.
1) Build as 32-bit gcc on SPARC 2) Build as 64-bit gcc on SPARC 3) Build as 32-bit with Sun's compiler on SPARC 4) Build as 64-bit with Sun's compiler on SPARC 5) Build as 32-bit gcc on x64 6) Build as 64-bit gcc on x64 7) Build as 32-bit with Sun's compiler on x86 8) Build as 64-bit with Sun's compiler on x64 (It should be noted, that the solving the first 4 will solve all of them, as anything that builds on SPARC will *normally* build on x86. There are exceptions of course). IMHO, before a new package in added to the Sage standard distribution, it should build under all these 8. Otherwise, it makes porting to a true 64-bit version of Sage more and more difficult, as more and more packages are added. Of course, we can have a long-term aim of having a 64-bit version building with the Sun compiler (the best solution for Solaris), but that aim will get become less and less practical if packages are added which don't build under these circumstances. The cliquer pagckage, which is up for review http://sagetrac.org/sage_trac/ticket/6681 certainly fails that, as the patched makefile has the line CC=gcc Hence I would be tempted to make that as 'with spgk, needs work', since it makes some pretty fundamental assumptions which will not be valid. --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
