On Jun 22, 4:44 pm, JohnBussoletti <[EMAIL PROTECTED]> wrote: Hi John,
> I tried to build sage-3.0.3 on my work system, a 64 bit dual core, > dual Xeon system running RHEL 4, I believe (output of cat /proc/ > version shows: > > Linux version 2.6.9-67.0.1.ELsmp ([EMAIL PROTECTED] > bc1-14.build.redhat.com) (gcc version 3.4.6 20060404 (Red Hat > 3.4.6-9)) #1 SMP Fri Nov 30 11:57:43 EST 2007 > > and uname -a shows: > > Linux mcneil.ca.boeing.com 2.6.9-67.0.1.ELsmp #1 SMP Fri Nov 30 > 11:57:43 EST 2007 x86_64 x86_64 x86_64 GNU/Linux ok. > While most libraries that were built were 64-bit, for some reason or > another the build of the various pieces of libgmp were done with > ABI=32 and this caused a failure to complete the sage build process > later on. > > I was able to download, build and install the libgmp stuff to the > sage-3.0.3/local directory (first time without the --enable-cxx flag) > and that build process correctly built the 64 bit versions. I then > continued the make process for sage and sage completed its build > without any errors, apparently successfully. However, when trying to > run sage the first time I get a core dump with a message > > ./sage > ---------------------------------------------------------------------- > | SAGE Version 3.0.3, Release Date: 2008-06-17 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > > init2.c:37: assertion failed: ((32 - 0)+0) == (((32 - 0)+0)/8) * 8 && > sizeof(mp_limb_t) == (((32 - 0)+0)/8) > /acct/jeb9140/sage/sage-3.0.3/local/bin/sage-sage: line 214: 10096 > Segmentation fault (core dumped) sage-ipython "$@" -c > "$SAGE_STARTUP_COMMAND;" > > which suspiciously looks like another possible inconsistency in 32 bit > versus 64 bit installation characteristics. > > Any suggestions on how to proceed? Can you post the output for at least one CPU from /proc/cpuinfo? We have had three similar build reports and will be switching to a fork of GMP in the near future. We have fixes for many of the misdetection issues with the latest Core2 and Xeon CPUs and those will be in the next Sage release. The above points to gmp itself, so can you build and compile a vanilla gmp 4.2.2 from sources and run make check and also verify that the output is truly a 64 bit library. It is very likely that you have a 64 bit gmp library on your system and some other component might have picked up a 32 bit gmp from the Sage build. > Note to William Stein: Thanks for your visit and presentation at > Boeing Commercial Airplanes a few weeks ago. 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 -~----------~----~----~----~------~----~------~--~---
