Sage 4.1.2.rc0 released

6 views
Skip to first unread message

Minh Nguyen

unread,
Oct 1, 2009, 3:39:04 AM10/1/09
to sage-devel, sage-release
Hi folks,

This is the first release candidate for Sage 4.1.2, which mostly fixed
bugs. With the Sage 4.1.2.rc0 release, I'm stepping down as release
manager for the 4.1.2 release cycle and hand over the release chair to
William Stein.

Binary for sage.math is available at

http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0-sage.math.washington.edu-x86_64-Linux.tar.gz

The source tarball is

http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0.tar

You can upgrade with the path

http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0/

Please test and report all issues.


* Known issues for OS X 10.6

This is our first port to Mac OS X 10.6 so there would be many more
bugs to iron out. The OS X 10.6 port is tracked at meta-ticket #6849
[1]. There are still some more packages to update/upgrade before the
OS X 10.6 is complete. I have listed various tickets on the milestone
page [3] that I think need to be resolved before releasing the stable
version of Sage 4.1.2. Please edit that page if there are any tickets
missing.


* Known issues for 64-bit Fedora 11 and 64-bit openSUSE 11.1

If you're going to upgrade to Sage 4.1.2.rc0 or build that version
from source, then you should use the cliquer spkg at ticket #6681 [2].
The version of cliquer that is shipped with Sage 4.1.2.rc0 is known to
fail to build on some 64-bit platforms.


The following tickets were merged in Sage 4.1.2.rc0:

#3951: Jason Grout: Make a "Tickets in which I have participated"
report [Reviewed by Minh Van Nguyen]
#6612: Harald Schilly: sage-update selects a suiteable mirror
[Reviewed by Minh Van Nguyen]
#6870: Hakan Granath: Bug in binomial [Reviewed by Karl-Dieter
Crisman, Adam Webb]
#6916: Minh Van Nguyen: follow-up to #6749: fix warnings when building
reference manual [Reviewed by William Stein, John Palmieri]
#7008: Jason Grout: consolidate in plotting all extraction of
variables, ranges, and fast_float setup [Reviewed by Karl-Dieter
Crisman]
#7020: Minh Van Nguyen: Fix 32-bit versus 64-bit boolean_function
issue in crypto [Reviewed by Jaap Spies]
#7022: William Stein: os x -- 10.6 -- generated the matplotlib font
cache crashes sage [Reviewed by Mike Hansen]
#7046: Ivan Andrus: Singular fails to build on OS X 10.6 with case
sensitive file system [Reviewed by William Stein, Minh Van Nguyen]
#7055: Georg S. Weber: Fix 32-bit versus 64-bit in pbori.pyx doctest
[Reviewed by Jaap Spies]
#7064: Minh Van Nguyen: fix warnings when building reference manual in
Sage 4.1.2.alpha4 [Reviewed by William Stein]

[1] http://trac.sagemath.org/sage_trac/ticket/6849

[2] http://trac.sagemath.org/sage_trac/ticket/6681

[3] http://trac.sagemath.org/sage_trac/milestone/sage-4.1.2

--
Regards
Minh Van Nguyen

davidloeffler

unread,
Oct 1, 2009, 7:36:53 AM10/1/09
to sage-devel
Building on 64-bit SuSE with SAGE_CHECK="yes" failed at libgcrypt,
with a bunch of errors in the gcrypt test script:

make[4]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
libgcrypt-1.4.3.p2/src/tests'
version:1.4.0:
ciphers:arcfour:blowfish:cast5:des:aes:twofish:serpent:rfc2268:seed:camellia:
pubkeys:dsa:elgamal:rsa:ecc:
digests:crc:md4:md5:rmd160:sha1:sha256:sha512:tiger:whirlpool:
rnd-mod:linux:
mpi-asm:amd64/mpih-add1.S:amd64/mpih-sub1.S:amd64/mpih-mul1.S:amd64/
mpih-mul2.S:amd64/mpih-mul3.S:amd64/mpih-lshift.S:amd64/mpih-rshift.S:
hwflist:
PASS: version
PASS: t-mpi-bit
PASS: prime
PASS: register
PASS: ac
PASS: ac-schemes
PASS: ac-data
Rijndael-128 test encryption failed.
algo 7, mode 1, gcry_cipher_setkey failed: Selftest failed
algo 7, mode 2, gcry_cipher_setkey failed: Selftest failed
algo 7, mode 5, gcry_cipher_setkey failed: Selftest failed
algo 7, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 7, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 7, mode 6, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 1, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 2, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 5, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 8, mode 6, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 1, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 2, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 5, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 3, gcry_cipher_setkey failed: Selftest failed
algo 9, mode 6, gcry_cipher_setkey failed: Selftest failed
aes-cbc-cts, gcry_cipher_setkey failed: Selftest failed
cbc-mac algo 7, gcry_cipher_setkey failed: Selftest failed
aes-ctr, gcry_cipher_setkey failed: Selftest failed
aes-cfb, gcry_cipher_setkey failed: Selftest failed
aes-ofb, gcry_cipher_setkey failed: Selftest failed
FAIL: basic
PASS: mpitests
PASS: tsexp
PASS: keygen
PASS: pubkey
PASS: hmac
PASS: keygrip
PASS: random
MD5 0ms 10ms 30ms
SHA1 0ms 10ms 70ms
RIPEMD160 10ms 10ms 40ms
TIGER192 0ms 20ms 30ms
SHA256 10ms 20ms 40ms
SHA384 10ms 20ms 40ms
SHA512 10ms 20ms 50ms
SHA224 10ms 20ms 40ms
MD4 0ms 10ms 30ms
CRC32 10ms 0ms 20ms
CRC32RFC1510 0ms 10ms 10ms
CRC24RFC2440 30ms 20ms 40ms
WHIRLPOOL 20ms 20ms 40ms

ECB CBC CFB
OFB CTR STREAM
--------------- --------------- ---------------
--------------- --------------- ---------------
3DES 70ms 70ms 80ms 70ms 70ms 70ms
70ms 80ms 80ms 80ms
CAST5 20ms 20ms 30ms 20ms 30ms 20ms
20ms 30ms 30ms 30ms
BLOWFISH 20ms 20ms 20ms 20ms 30ms 20ms
30ms 20ms 40ms 30ms
AES Rijndael-128 test encryption failed.
gcry_cipher_setkey failed: Selftest failed
FAIL: benchmark
========================================
2 of 16 tests failed
Please report to bug-li...@gnupg.org
========================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
libgcrypt-1.4.3.p2/src/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
libgcrypt-1.4.3.p2/src/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
libgcrypt-1.4.3.p2/src'
make check failed for libgcrypt
*************************************
Error testing package ** libgcrypt-1.4.3.p2 **
*************************************
Message has been deleted

davidloeffler

unread,
Oct 1, 2009, 7:48:35 AM10/1/09
to sage-devel
I will give it a try once the current build has finished.

David

On Oct 1, 12:39 pm, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi David,
>
> On Thu, Oct 1, 2009 at 9:36 PM, davidloeffler <dave.loeff...@gmail.com> wrote:
>
> > Building on 64-bit SuSE with SAGE_CHECK="yes" failed at libgcrypt,
> > with a bunch of errors in the gcrypt test script:
>
> Can you try using the updated libgcrypt spkg at ticket #7045 [1]?
>
> [1]http://trac.sagemath.org/sage_trac/ticket/7045

John Cremona

unread,
Oct 1, 2009, 8:51:57 AM10/1/09
to sage-...@googlegroups.com
Two success stories for 4.1.2.rc0: build ok , testall ok: Both are 64-bit Suse.

1. Linux version 2.6.24-19-generic (buildd@yellow) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:15:37 UTC 2008

2. Linux version 2.6.28-13-generic (buildd@yellow) (gcc version 4.3.3
(Ubuntu 4.3.3-5ubuntu4) ) #44-Ubuntu SMP Tue Jun 207:55:09 UTC 2009

One failure, on 32-bit Suse, building R (in 4.1.2.alpha4). The tail
end of the install log is here:

make[6]: Leaving directory
`/local/jec/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src/src/library/base'
/home/masgaj/local/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src/bin/exec/R:
/local/jec/sage-4.1.2.alpha4/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3/libgcc_s.so.1:
version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
make[5]: *** [all] Error 1
make[5]: Leaving directory
`/local/jec/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src/src/library/base'
make[4]: *** [R] Error 1
make[4]: Leaving directory
`/local/jec/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src/src/library'
make[3]: *** [R] Error 1
make[3]: Leaving directory
`/local/jec/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src/src'
make[2]: *** [R] Error 1
make[2]: Leaving directory `/local/jec/sage-4.1.2.alpha4/spkg/build/r-2.9.2/src'
Error building R.

real 1m13.819s
user 0m50.979s
sys 0m20.997s
sage: An error occurred while installing r-2.9.2

The system is
Linux version 2.6.27.29-0.1-pae (geeko@buildhost) (gcc version 4.3.2
[gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2009-08-15
17:53:59 +0200
and I don't have root access to it.

John

2009/10/1 Minh Nguyen <nguye...@gmail.com>:

davidloeffler

unread,
Oct 1, 2009, 9:47:09 AM10/1/09
to sage-devel
I've come up with another error. This is the first time I've built
with SAGE_CHECK set, so it's running all the test suites in all the
packages, and quaddouble fails:

Successfully installed quaddouble-2.2.p9
Running the test suite.
make[2]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src'
Making check in
config
make[3]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/config'
make[3]: Nothing to be done for
`check'.
make[3]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/config'
Making check in
src
make[3]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/src'
make[3]: Nothing to be done for
`check'.
make[3]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/src'
Making check in
include
make[3]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/include'
make[3]: Nothing to be done for
`check'.
make[3]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/include'
Making check in tests
make[3]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/tests'
make qd_test pslq_test
make[4]: Entering directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/tests'
g++ -DHAVE_CONFIG_H -I.. -I../include -I../include -fPIC -O3 -
Dx86 -MT qd_test.o -MD -MP -MF .deps/qd_test.Tpo -c -o qd_test.o
qd_test.cpp
qd_test.cpp:25: error: ‘std::strcmp’ has not been declared
qd_test.cpp:26: error: ‘std::exit’ has not been declared
qd_test.cpp: In function ‘int main(int, char**)’:
qd_test.cpp:374: error: ‘strcmp’ was not declared in this scope
qd_test.cpp:376: error: ‘exit’ was not declared in this scope
make[4]: *** [qd_test.o] Error 1
make[4]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/david/sage-4.1.2.rc0/spkg/build/
quaddouble-2.2.p9/src'
*************************************
Error testing package ** quaddouble-2.2.p9 **
*************************************

This looks like a bug in the quaddouble test script, rather than in
quaddouble itself.

William Stein

unread,
Oct 1, 2009, 11:14:24 AM10/1/09
to sage-release, sage-devel
Hi,

Here are links to the docs in sage-4.1.2.rc0:

http://sage.math.washington.edu/home/mvngu/release/sage-4.1.2.rc0/devel/sage/doc/output/html/en/

If anybody wants to skim them and make a list of issues you see, that
would be appreciated.

William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

William Stein

unread,
Oct 1, 2009, 11:15:05 AM10/1/09
to sage-...@googlegroups.com

We were supposed to remove quaddouble from sage long ago. Maybe now
is the time.

William

davidloeffler

unread,
Oct 1, 2009, 11:23:25 AM10/1/09
to sage-devel
On Oct 1, 4:15 pm, William Stein <wst...@gmail.com> wrote:
> On Thu, Oct 1, 2009 at 6:47 AM, davidloeffler <dave.loeff...@gmail.com> wrote:
>
> > I've come up with another error. This is the first time I've built
> > with SAGE_CHECK set, so it's running all the test suites in all the
> > packages, and quaddouble fails:

The list of standard Sage packages that fail their own test suites is
getting worryingly long -- as well as quaddouble and libgcrypt, I'm
getting failures from R, pyprocessing, and sqlalchemy.

William Stein

unread,
Oct 1, 2009, 11:28:29 AM10/1/09
to sage-...@googlegroups.com

Pyprocessing is a standard part of Python 2.6, so I have no idea why
it's included in Sage as a separate package. Removing it is trac
6503:

http://trac.sagemath.org/sage_trac/ticket/6503

Unfortunately, I can't think of an argument to remove R or sqlalchemy! :-)

Open tickets for the check failures of those.

William

Jaap Spies

unread,
Oct 1, 2009, 11:32:07 AM10/1/09
to sage-...@googlegroups.com
Minh Nguyen wrote:
> Hi folks,
>
> This is the first release candidate for Sage 4.1.2, which mostly fixed
> bugs. With the Sage 4.1.2.rc0 release, I'm stepping down as release
> manager for the 4.1.2 release cycle and hand over the release chair to
> William Stein.
>
> Binary for sage.math is available at
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0-sage.math.washington.edu-x86_64-Linux.tar.gz
>
> The source tarball is
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0.tar
>
> You can upgrade with the path
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0/
>
> Please test and report all issues.
>
>

On Fedora 11, 32 bit an upgrade from alpha4 had success:

----------------------------------------------------------------------
All tests passed!

Jaap

davidloeffler

unread,
Oct 1, 2009, 11:50:08 AM10/1/09
to sage-devel


On Oct 1, 12:39 pm, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi David,
>
> On Thu, Oct 1, 2009 at 9:36 PM, davidloeffler <dave.loeff...@gmail.com> wrote:
>
> > Building on 64-bit SuSE with SAGE_CHECK="yes" failed at libgcrypt,
> > with a bunch of errors in the gcrypt test script:
>
> Can you try using the updated libgcrypt spkg at ticket #7045 [1]?
>
> [1]http://trac.sagemath.org/sage_trac/ticket/7045
>
> --
> Regards
> Minh Van Nguyen

The new spkg 1.4.4.p0 seems to fix the problem.

David

davidloeffler

unread,
Oct 1, 2009, 12:01:53 PM10/1/09
to sage-devel


On Oct 1, 4:28 pm, William Stein <wst...@gmail.com> wrote:
These are now #7090 and #7091.

Marshall Hampton

unread,
Oct 1, 2009, 12:53:22 PM10/1/09
to sage-devel
I have only one test failure on sage-4.1.2.rc0; I also had it on the
alpha4:

File "/Volumes/E/sage-4.1.2.rc0/devel/sage/sage/server/notebook/
cell.py", line 1601:
sage: C.introspect_html()
Expected:
'<div class="docstring">...<span class="math">foobar</span>...</
div>'
Got:
'<div class="docstring"><pre>foobar</pre></div>'


This is on an intel Mac Pro running OS 10.4.11

-Marshall

Jaap Spies

unread,
Oct 1, 2009, 12:55:14 PM10/1/09
to sage-...@googlegroups.com
Minh Nguyen wrote:
> Hi folks,
>
> This is the first release candidate for Sage 4.1.2, which mostly fixed
> bugs. With the Sage 4.1.2.rc0 release, I'm stepping down as release
> manager for the 4.1.2 release cycle and hand over the release chair to
> William Stein.
>
> Binary for sage.math is available at
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0-sage.math.washington.edu-x86_64-Linux.tar.gz
>
> The source tarball is
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0.tar
>
> You can upgrade with the path
>
> http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.rc0/
>
> Please test and report all issues.
>

On a fresh install on Fedora 11, 32 bit as expected the build of
pari-2.3.3.p1 failed:

gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o base3.o ../src/basemath/base3.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make[3]: *** [base3.o] Error 1
make[3]: Leaving directory `/home/jaap/downloads/sage-4.1.2.rc0/spkg/build/pari-2.3.3.p1/src/Olinux-i686'
make[2]: *** [gp] Error 2
make[2]: Leaving directory `/home/jaap/downloads/sage-4.1.2.rc0/spkg/build/pari-2.3.3.p1/src'
Error building GP

real 37m26.888s
user 31m48.467s
sys 0m33.612s
sage: An error occurred while installing pari-2.3.3.p1

Someone (me?) should open a track ticket.

Jaap

Minh Nguyen

unread,
Oct 1, 2009, 12:59:23 PM10/1/09
to sage-...@googlegroups.com
Hi Jaap,

On Fri, Oct 2, 2009 at 2:55 AM, Jaap Spies <j.s...@hccnet.nl> wrote:

<SNIP>

> Someone (me?) should open a track ticket.

That would be great! Can you please do that? There's no Fedora 11
machines on the Sage build farm to test the updated Pari package if
someone happens to update it to fix this build issue on Fedora 11.

Jaap Spies

unread,
Oct 1, 2009, 1:03:37 PM10/1/09
to sage-...@googlegroups.com

I don't think one needs a Fedora 11, 32 bits machine to fix this!
All what has to be done is a patch of the pari spkg to work around
this gcc problem for the moment. There eventually be a fix in gcc
distributed with Fedora and some other linus distros.

Jaap


Jaap Spies

unread,
Oct 1, 2009, 1:15:36 PM10/1/09
to sage-...@googlegroups.com

Håkan Granath

unread,
Oct 1, 2009, 3:20:37 PM10/1/09
to sage-devel
> Here are links to the docs in sage-4.1.2.rc0:
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.2.rc0/dev...
>
> If anybody wants to skim them and make a list of issues you see, that
> would be appreciated.

A minor point: some documentation on keyboard shortcuts was added to
the reference manual in #6556, but the sage/server/notebook/config
section
was removed in #6840.

/Håkan

John H Palmieri

unread,
Oct 1, 2009, 9:03:59 PM10/1/09
to sage-devel
On Oct 1, 12:39 am, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi folks,
>
> This is the first release candidate for Sage 4.1.2, which mostly fixed
> bugs. With the Sage 4.1.2.rc0 release, I'm stepping down as release
> manager for the 4.1.2 release cycle and hand over the release chair to
> William Stein.

OS X 10.5:

32-bit: built fine and all tests passed.

64-bit: with the cliquer package from #6681, built fine. (I didn't
even try with the old version of cliquer; should I have?) One doctest
failure:

sage -t -long "devel/sage/sage/structure/parent.pyx"
**********************************************************************
File "/Applications/sage_builds/sage-4.1.2.rc0-64bit/devel/sage/sage/
structure/parent.pyx", line 365:
sage: sqrt(2) in CC
Expected:
True
Got:
False
**********************************************************************

This doctest passed when I tried it again -- I tried about a dozen
times, with success every time. I feel as though I've seen this
before, but I don't remember when.

John

Kiran Kedlaya

unread,
Oct 1, 2009, 10:12:05 PM10/1/09
to sage-devel
On Oct 1, 3:39 am, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi folks,
>
> This is the first release candidate for Sage 4.1.2, which mostly fixed
> bugs. With the Sage 4.1.2.rc0 release, I'm stepping down as release
> manager for the 4.1.2 release cycle and hand over the release chair to
> William Stein.
>
Using the updated cliquer package from #6681, on my 64-bit Fedora 10
machine, 4.1.2rc0 builds and passes all long doctests except for
these:

sage -t -long "devel/sage/sage/server/notebook/notebook.py"
sage -t -long "devel/sage/sage/interfaces/sage0.py"

However, I wasn't able to reproduce these failures. The second one
looks like an out-of-memory or something. The first is at line 1475;
it looks like the "xxx seconds ago" at the end of the docstring became
"1 second ago" in my first test.

Kiran

Pat LeSmithe

unread,
Oct 2, 2009, 3:56:35 AM10/2/09
to sage-...@googlegroups.com
Håkan Granath wrote:
> A minor point: some documentation on keyboard shortcuts was added to
> the reference manual in #6556, but the sage/server/notebook/config
> section
> was removed in #6840.

Thanks very much for pointing this out. I'll create a new ticket and
patch to bring config.py back into the manual.

Minh Nguyen

unread,
Oct 3, 2009, 3:20:25 AM10/3/09
to sage-devel
On Thu, Oct 1, 2009 at 5:39 PM, Minh Nguyen <nguye...@gmail.com> wrote:

<SNIP>

> Please test and report all issues.

Sage 4.1.2.rc0 build and pass all doctests (also with the "-long"
option) on the following platforms:

* eno: 64-bit Fedora 9 with GCC 4.4.1
* lena: 64-bit Red Hat Enterprise Linux Server 5.3 with GCC 4.4.1
* menas: 64-bit openSUSE 11.1 with GCC 4.4.1
* rosemary: 64-bit Red Hat Enterprise Linux Server 5.4
* sage: 64-bit Ubuntu 8.04.3 LTS

MaxTheMouse

unread,
Oct 4, 2009, 5:19:36 AM10/4/09
to sage-devel

>
> Sage 4.1.2.rc0 build and pass all doctests (also with the "-long"
> option) on the following platforms:
>
> * eno: 64-bit Fedora 9 with GCC 4.4.1
> * lena: 64-bit Red Hat Enterprise Linux Server 5.3 with GCC 4.4.1
> * menas: 64-bit openSUSE 11.1 with GCC 4.4.1
> * rosemary: 64-bit Red Hat Enterprise Linux Server 5.4
> * sage: 64-bit Ubuntu 8.04.3 LTS
>
> --
> Regards
> Minh Van Nguyen

I was able to build and successfully test on Ubuntu 9.04 (AMD64) and
9.10 beta (AMD64). I also set SAGE_FORTRAN to use the installed
gfortran. I used the new packages mentioned above.
cliquer-1.2.p0.spkg #6681
libgcrypt-1.4.4.p0.spkg #7045

I did not make any changes to Pari and it worked. Apparently the gcc
bug fix is already out. (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu5))

When I tried with SAGE_CHECK="yes" I got the same problems as already
reported so these are with it off. I used 'make testlong' in both
cases.

Cheers,
Adam
Reply all
Reply to author
Forward
0 new messages