On 09/ 7/10 08:20 AM, Mitesh Patel wrote:
On 08/24/2010 08:01 PM, William Stein wrote:
On Tue, Aug 24, 2010 at 1:38 PM, William Stein<wst...@gmail.com> wrote:
On Mon, Aug 23, 2010 at 8:25 PM, Jonathan Hanke<jonha...@gmail.com> wrote:
Hi,
I'm trying to build sage 4.5.2 on a Sun Fire X4450 server (Intel Xenon
processors) running Redhat linux (Enterprise edition), and get an error when
building Atlas in the make script. Any comments are appreciated. Thanks,
I just tried building 4.5.3.alpha2 on *your* computer (rosemary) in
/home/wstein/build/sage-4.5.3.alpha2 and it worked fine. Note that I
set this environment variable:
export SAGE_FAT_BINARY=yes
This changes how ATLAS is built to use a sort of "lowest common
denominator" configuration.
You might try that. It can potentially make numerical linear algebra
slower for you, but I doubt
you do a lot of that.
I waited for the Sage testsuite to run on rosemary (with
sage-4.5.3.alpha2), and interestingly
there are a huge number of failures, despite the building completing
fine. It looks like
every failure is "ImportError: No module named scipy". This suggests
that despite the build
of Sage exiting with an error, for some reason the exit code was still
zero, so the testsuite got run.
Checking further I see that PIL failed to build:
/usr/bin/ld: skipping incompatible /usr/lib/libjpeg.so when searching for -ljpeg
/usr/bin/ld: /usr/local/lib/libpython2.6.a(abstract.o): relocation R_X86_64_32 a
gainst `a local symbol' can not be used when making a shared object; recompile w
ith -fPIC
/usr/local/lib/libpython2.6.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1
Error building PIL: 'Error installing PIL'
real 0m10.521s
user 0m8.155s
sys 0m2.290s
sage: An error occurred while installing pil-1.1.6.p2
--
This means that building Sage-4.5.3 at least is totally broken on
rosemary.math.uga.edu. This could be the result of you installing a
new systemwide package, or something else (I don't know).
The PIL error is
http://trac.sagemath.org/sage_trac/ticket/9864
See
http://groups.google.com/group/sage-devel/msg/fbd62a23fe1dcffa?hl=en-GB&;
This boils down to the fact the wrong Python libraries are used - see #9209.
This has bugged me on some Solaris systems, and seems to be an issue on Red Hat
Linux too.
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
