I managed to get a successful build of sage-3.0.3 on a 64 bit Xeon Linux system. The problem is the the gmp-4.2.2 included in the sage distribution is either a mix of earlier releases (gmp-4.2.1) or is an eaerlier release (gmp-4.2.1). Replacing the gmp-4.2.2.spkg file with an spkg file built with the "real" gmp-4.2.2 allowed me to get a successful build.
As a guide to others: I downloaded the gmp-4.2.2.tar.gz package from the gmp web site and extracted it into a directory ~/Dowload/gmp-4.2.2 With the knowledge that an spkg file is really a tar.bz2 file, I went to the sage-3.0.3 directory and descended to the spkg/standard directory, built a tmp directory in it and did the following: cd tmp cp gmp-4.2.2.spkg gmp.tar.bz2 tar jxf gmp.tar.bz2 and a gmp-4.2.2 directory appeared within the tmp directory. Then I did cd gmp-4.2.2 cd src rm -r * cd .. (edit sage-install script to remove any of the patch operations and make them into simply an 'echo "Nothing to do" ' command....) cp -r ~/Download/gmp-4.2.2/* src cd .. rm gmp.tar.bz2 tar jcf gmp.new gmp-4.2.2 cp gmp.new ../gmp-4.2.2.spkg cd .. rm -r tmp and then I was able to successfully build sage-3.0.3 on a Xeon 64 bit RHEL 4 system. On Jun 24, 7:10 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Jun 24, 6:59 pm, JohnBussoletti <[EMAIL PROTECTED]> wrote: > > > Michael, > > Hi John, > > > I interrupted the sage build during the construction of gmp, went to > > the spkg/build/gmp-4.2.2/src directory and diff-ed the configure file > > against the configure file that I obtained from a direct download of > > gmp-4.2.2 > > > I discovered that while the gmp spkg claims to be 4.2.2, the configure > > script is from gmp-4.2.1 and is missing a number of items that relate > > to the definition of the ABI environment variable, particularly for > > x86_64 systems. Could it be that someone inadvertently packaged > > gmp-4.2.1? > > Nope, the confiure script in patches is old and during the update that > was not fixed. > > > I saw in an earlier post from WIlliam Stein that the spkg is just a > > compressed tar file, but when I looked at the directory structure of > > the gmp-4.4.2 from the sage-3.0.3 package, it had some added > > directories (e.g., patch) and the src directory seemed to contain the > > libgmp-4.2.2 contents. Can I try to build my own spkg for gmp-4.2.2? > > Sure, all you need is a script called spkg-install that builds the > package and install is into $SAGE_LOCAL. > > > The initialization problem seems to be coming from an assert inside > > some libgmp code, so the problem may end up just being with libgmp. > > If there are any headers from libgmp that were used in the build of > > subsequent sage objects, that might explain the abort that I see when > > sage initializes. > > Yes, I suspected something similar. > > > I'll give sage-3.0.4.alpha1 a go and see what happens. And I'll also > > try to build my own gmp-4.2.2 spkg and see how that goes. > > > John Bussoletti > > Thanks for poking around :) > > As is I am working on two blockers, i.e.#3508 (GMP fixes) and #3486 > (NTL with csh and gcc 4.3 broken) before releasing Sage 3.0.4.alpha1 > and a couple more fixes I am currently merging and testing. > > You can find details to the tickets > athttp://trac.sagemath.org/sage_trac/ticket/3508 > for example. If you want a trac account just write me an email off > list. > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
