sage-4.7.1.rc1 released
Jeroen Demeyer
We're releasing Sage 4.7.1.rc1.
Source archive:
http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1.tar
Upgrade path:
http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1/
The source and upgrade path can also be found on the mirror network
(you might need to wait a while before the mirrors are synchronized):
http://www.sagemath.org/download-latest.html
Please build, test, and report! We'd love to hear about your
experiences with this release.
== Tickets ==
* We closed 202 tickets in this release. For details, see
http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/tickets.html
Closed tickets:
#5367: bug in composition of power series [Reviewed by David Loeffler]
#10240: Dmitrii Pasechnik: pari-2.4.3.svn-12577.p9 incorrectly checks
for the shared library on Cygwin [Reviewed by Karl-Dieter Crisman]
#10749: libpng-1.2.35.p2 has syntax errors in its spkg-install [Reviewed
by Mariah Lenox]
#11496: Add jmol script in SAGE_ROOT/local/bin to hg and update
[Reviewed by John Palmieri]
#11561: Python spkg fails to build on Debian Wheezy/Sid. [Reviewed by
Jean-Pierre Flori]
Merged in sage-4.7.1.rc1:
#11605: Dima Pasechnik, Leif Leonhardy: Typos in PARI's spkg-install
(2.4.3.alpha.p5) [Reviewed by Jeroen Demeyer]
#11609: Jim Kleckner: fix some minor typos in the *documentation* of
Hidden Markov Models [Reviewed by William Stein]
Jaap Spies
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1.tar
>
On Fedora 15 64 bit make ptestlong with 8 threads:
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 1893.8 seconds
[jaap@vrede sage-4.7.1.rc1]$
Jaap
john.hoebing
as of today, compiling sage-4.7.1.rc1:
...
/usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
symbol 'dlclose@@GLIBC_2.2.5'
/usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
x86_64-linux-gnu/libdl.so so try adding it to the linker command line
/usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
operation
collect2: ld returned 1 exit status
make[4]: *** [iparith.inc] Error 1
make[4]: *** Waiting for unfinished jobs....
/usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
symbol 'dlclose@@GLIBC_2.2.5'
/usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
x86_64-linux-gnu/libdl.so so try adding it to the linker command line
/usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
operation
collect2: ld returned 1 exit status
...
And here's the 'gcc -v':
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/
4.6.1/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.6.1-5ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.6/
README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/
usr --program-suffix=-4.6 --enable-shared --enable-multiarch --with-
multiarch-defaults=x86_64-linux-gnu --enable-linker-build-id --with-
system-zlib --libexecdir=/usr/lib/x86_64-linux-gnu --without-included-
gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/
4.6 --libdir=/usr/lib/x86_64-linux-gnu --enable-nls --with-sysroot=/ --
enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-
time=yes --enable-plugin --enable-objc-gc --disable-werror --with-
arch-32=i686 --with-tune=generic --enable-checking=release --
build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-
gnu
Thread model: posix
gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-5ubuntu2)
$
...
I don't know if anyone is claiming that gcc-4.6.1 is supposed to
build sage, but in any case it doesn't build it on the oneiric alpha2
release as of today.
Francois Bissey
you should precise that the failure is in building singular [says he who has
spend too much on it and can recognize file names immediately]. Just tell us
if I am wrong.
Francois
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
Francois Bissey
> On Mon, 25 Jul 2011 20:52:59 john. hoebing wrote:
> > Here's Ubuntu 11.10 alpha2 updated with the latest gcc-4.6.1
> > as of today, compiling sage-4.7.1.rc1:
> >
> > ...
> > /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> > symbol 'dlclose@@GLIBC_2.2.5'
> > /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> > x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> > /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> > operation
> > collect2: ld returned 1 exit status
> > make[4]: *** [iparith.inc] Error 1
> > make[4]: *** Waiting for unfinished jobs....
> > /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> > symbol 'dlclose@@GLIBC_2.2.5'
> > /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> > x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> > /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> > operation
> > collect2: ld returned 1 exit status
> > ...
/usr/lib/x86_64-linux-gnu/libdl.so
or possibly
/usr/lib64/x86_64-linux-gnu/libdl.so
on your system? If not, finding .deb providing it would be a start.
john.hoebing
Here's my libdl locate:
$ locate libdl
/lib/x86_64-linux-gnu/libdl-2.13.so
/lib/x86_64-linux-gnu/libdl.so.2
/lib32/libdl-2.13.so
/lib32/libdl.so.2
/usr/lib/x86_64-linux-gnu/libdl.a
/usr/lib/x86_64-linux-gnu/libdl.so
$
The symbolic links look correct too, and it shouldn't be
using the lib32 versions. Hope it helps.
John Hoebing
On Jul 25, 9:48 pm, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
Volker Braun
John Cremona
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1.tar
>
Built fine and all tests pass (make ptestlong) on 64-bit ubuntu.
John
tvn
Justin C. Walker
On Jul 25, 2011, at 06:03 , Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1/
Built on Mac OS X, 10.6.8 (Dual 6-Core Xeon) as an upgrade to 4.7. No problems in build and all tests passed!
Justin
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
If it weren't for carbon-14, I wouldn't date at all.
-----------
Dr. David Kirkby
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7.1.rc1.tar
On OpenSolaris I got a failure when running "ptestlong"
The following tests failed:
sage -t -long -force_lib devel/sage/sage/modular/hecke/homspace.py # 0
doctests failed
----------------------------------------------------------------------
Total time for all tests: 1936.1 seconds
It's failing with:
sage -t -long -force_lib devel/sage/sage/modular/hecke/homspace.py
python: can't open file '/export/home/drkirkby/.sage//tmp/homspace.py': [Errno
2] No such file or directory
But when I run the test on its own:
drkirkby@hawk:~/sage-4.7.1.rc1$ ./sage -t -long -force_lib
devel/sage/sage/modular/hecke/homspace.py
sage -t -long -force_lib "devel/sage/sage/modular/hecke/homspace.py"
[3.3 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 3.3 seconds
So I assume this is the usual problem of parallel tests overwriting the results
from other tests, but perhaps I'm wrong.
Dave
leif
> On 07/25/11 02:03 PM, Jeroen Demeyer wrote:
>> We're releasing Sage 4.7.1.rc1.
>
>
> The following tests failed:
>
> sage -t -long -force_lib devel/sage/sage/modular/hecke/homspace.py
> # 0 doctests failed
> ----------------------------------------------------------------------
> Total time for all tests: 1936.1 seconds
>
> It's failing with:
>
> sage -t -long -force_lib devel/sage/sage/modular/hecke/homspace.py
> python: can't open file '/export/home/drkirkby/.sage//tmp/homspace.py':
> [Errno 2] No such file or directory
>
>
> But when I run the test on its own:
>
> drkirkby@hawk:~/sage-4.7.1.rc1$ ./sage -t -long -force_lib
> devel/sage/sage/modular/hecke/homspace.py
> sage -t -long -force_lib "devel/sage/sage/modular/hecke/homspace.py"
> [3.3 s]
>
> ----------------------------------------------------------------------
> All tests passed!
> Total time for all tests: 3.3 seconds
>
>
> So I assume this is the usual problem of parallel tests overwriting the
> results from other tests, but perhaps I'm wrong.
Apparently. We have both
devel/sage/sage/modular/abvar/homspace.py and
devel/sage/sage/modular/hecke/homspace.py
so it's rather unlikely to happen (compared to the frequency of other
files with identical basenames), but not impossible.
-leif
leif
> Dr. David Kirkby wrote:
>> sage -t -long -force_lib devel/sage/sage/modular/hecke/homspace.py
>> python: can't open file '/export/home/drkirkby/.sage//tmp/homspace.py':
>> [Errno 2] No such file or directory
>>
>>
>> But when I run the test on its own:
>>
>> drkirkby@hawk:~/sage-4.7.1.rc1$ ./sage -t -long -force_lib
>> devel/sage/sage/modular/hecke/homspace.py
>> sage -t -long -force_lib "devel/sage/sage/modular/hecke/homspace.py"
>> [3.3 s]
>>
>> ----------------------------------------------------------------------
>> All tests passed!
>> Total time for all tests: 3.3 seconds
>>
>>
>> So I assume this is the usual problem of parallel tests overwriting the
>> results from other tests, but perhaps I'm wrong.
>
> Apparently. We have both
>
> devel/sage/sage/modular/abvar/homspace.py and
> devel/sage/sage/modular/hecke/homspace.py
>
> so it's rather unlikely to happen (compared to the frequency of other
> files with identical basenames), but not impossible.
Note that you perhaps should rerun the tests of the first one as well,
as the sequence might actually even have been:
- create file with tests for the first
- create file with tests for the second
- run Python on the tests of the first (which are now those of the second)
- delete file with tests for the first
(first file only *seems* to have passed all tests)
- run Python on the tests for the second (which just got deleted - Errno 2)
- [try to delete the already deleted file]
-leif
Dr. David Kirkby
I've re-run both tests individually several times in a random order and always
pass.
I thought someone had done quite a bit of work on fixing this issue of the
random doctest failures due to similar basenames. I'm a bit surprised that this
problem is still outstanding.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
leif
Yep, I also assumed a while ago it had meanwhile been fixed. It's
http://trac.sagemath.org/sage_trac/ticket/9739, "currently" still
needing work for some reason. (You're cc'ed on that btw.)
The only action that has happened there in the last few (seven to nine)
month was that of a spammer and postponing the milestone... :-/
-leif
See also http://trac.sagemath.org/sage_trac/ticket/11337 for a
doctesting meta-ticket.
luisfe
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
4.6.1
All tests passed!
Total time for all tests: 5063.0 seconds
I have realized that ATLAS takes ages to compile on new sandy-bridge
processors, due to the lack of preconfigured optimization options.
slelievre
> Dear Sage lovers
> We're releasing Sage 4.7.1.rc1.
Thank you! Here are the install results in four different setups.
- intel Mac, Mac OS X 10.5.8, XCode 3.1.4, gcc 4.0.1: testlong ok.
- intel Mac, Mac OS X 10.5.8, XCode 3.1.4, gcc 4.2.1: testlong ok.
- PPC G4 Mac, Mac OS X 10.5.8, XCode 3.1.4, gcc 4.0.1:
stays stuck while installing R, last line displayed is:
begin installing recommended package survival
- intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
testlong fails on interrupt.pyx ("killed by signal 11")
Samuel
Jean-Pierre Flori
experimental.
All tests passed!
Total time for all tests: 3091.8 seconds
Jeroen Demeyer
> - intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
> testlong fails on interrupt.pyx ("killed by signal 11")
Are you able to give me shell access on such a machine? I know this
error occurs on *some* OS X systems, but I have not been able to
reproduce it myself. The ticket is #11545 by the way.
William Stein
The above specs sound just like those of bsd.math.washington.edu,
which you (jdmeyer) have shell access to (as "jdmeyer").
-- Wiliam
>
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To post to this group, send email to sage-r...@googlegroups.com.
> To unsubscribe from this group, send email to sage-release...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
>
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
Jeroen Demeyer
> On Thu, Jul 28, 2011 at 1:14 PM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:
>> On 2011-07-27 14:00, slelievre wrote:
>>> - intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
>>> testlong fails on interrupt.pyx ("killed by signal 11")
>>
>> Are you able to give me shell access on such a machine? I know this
>> error occurs on *some* OS X systems, but I have not been able to
>> reproduce it myself. The ticket is #11545 by the way.
>
> The above specs sound just like those of bsd.math.washington.edu,
> which you (jdmeyer) have shell access to (as "jdmeyer").
The mentioned issue does not occur on bsd, I have done many tests.
I don't know why, but it really appears only on a small but
non-negligable subset of OS X machines.
kcrisman
> stays stuck while installing R, last line displayed is:
> begin installing recommended package survival
type of box (10.4, however) next week. I haven't seen that before,
and I note you had it in rc0 as well. Did you try any previous
alphas? Any additional info would be helpful (no error messages in
the R install?).
Thanks!
- kcrisman
leif
> slelievre wrote:
>> - PPC G4 Mac, Mac OS X 10.5.8, XCode 3.1.4, gcc 4.0.1:
>> stays stuck while installing R, last line displayed is:
>> begin installing recommended package survival
>
> Hmm, odd. I'll try to check that out when I get access to the correct
> type of box (10.4, however) next week.
Dima (trac: dimpase) also has a PPC (G4) with MacOS X 10.5 (Darwin
9.8.0), but gcc version 4.2.1 (Apple Inc. build 5577).
I don't know if he tried to build any recent alpha/rc on it though.
At least the linker of his version ([also] part of XCode, apparently the
same as with gcc 4.0.1) is buggy (e.g. when debug symbols are used, cf.
#5847).
The R spkg itself hasn't changed since Sage 4.6.alpha2 (it's still
r-2.10.1.p4) btw., so if any Sage version since then *did* build on
Samuel's PPC, the error must originate from something else.
(We e.g. already had strange errors when some environment variables
related to R had been set; I'm not sure if this has meanwhile at least
partially been fixed in some other Sage script. Another possibility are
components used by R; the ones shipped with Sage are ATLAS [not built on
MacOS X as it has its own Apple version], Fortran, iconv, readline and
Python, and perhaps also LAPACK and libpng.)
Just my 2 ct,
-leif
Kiran Kedlaya
matters). Typical example:
sage -t -long -force_lib "devel/sagenb-main/sagenb/storage/
abstract_storage.py"
Traceback (most recent call last):
File "/home/r1/kedlaya/.sage//tmp/abstract_storage.py", line 2, in
<module>
from sage.all_cmdline import *;
File "/scratch/sage-4.7.1.rc1/local/lib/python/site-packages/sage/
all_cmdline.py", line 14, in <module>
from sage.all import *
File "/scratch/sage-4.7.1.rc1/local/lib/python/site-packages/sage/
all.py", line 60, in <module>
import twisted.persisted.styles
File "/scratch/sage-4.7.1.rc1/local/lib/python2.6/site-packages/
Twisted-9.0.0-py2.6-linux-x86_64.egg/twisted/persisted/styles.py",
line 22, in <module>
from twisted.python import log
File "/scratch/sage-4.7.1.rc1/local/lib/python2.6/site-packages/
Twisted-9.0.0-py2.6-linux-x86_64.egg/twisted/python/log.py", line 17,
in <module>
from zope.interface import Interface
File "/home/sdb1/r1/kedlaya/.sage/tmp/zope.py", line 33, in <module>
from connector import *
File "/home/sdb1/r1/kedlaya/.sage/tmp/connector.py", line 33, in
<module>
from fckconnector import FCKeditorConnectorBase # import base
connector
File "/home/sdb1/r1/kedlaya/.sage/tmp/fckconnector.py", line 28, in
<module>
import cgi, os
File "/home/sdb1/r1/kedlaya/.sage/tmp/cgi.py", line 3, in <module>
import urllib
File "/home/sdb1/r1/kedlaya/.sage/tmp/urllib.py", line 30, in
<module>
from urlparse import urljoin as basejoin
File "/home/sdb1/r1/kedlaya/.sage/tmp/urlparse.py", line 84, in
<module>
from collections import namedtuple
File "/home/sdb1/r1/kedlaya/.sage/tmp/collections.py", line 10, in
<module>
from keyword import iskeyword as _iskeyword
File "/home/sdb1/r1/kedlaya/.sage/tmp/keyword.py", line 84, in
<module>
from mercurial import commands, cmdutil, dispatch, filelog,
revlog, extensions
File "/scratch/sage-4.7.1.rc1/local/lib/python2.6/mercurial/
commands.py", line 9, in <module>
from lock import release
File "/scratch/sage-4.7.1.rc1/local/lib/python2.6/mercurial/
lock.py", line 8, in <module>
import util, error
File "/scratch/sage-4.7.1.rc1/local/lib/python2.6/mercurial/
util.py", line 18, in <module>
import errno, re, shutil, sys, tempfile, traceback
File "/home/sdb1/r1/kedlaya/.sage/tmp/tempfile.py", line 34, in
<module>
from random import Random as _Random
File "/home/sdb1/r1/kedlaya/.sage/tmp/random.py", line 30, in
<module>
from Crypto import Random
File "/scratch/sage-4.7.1.rc1/local/lib/python/site-packages/Crypto/
Random/__init__.py", line 29, in <module>
import _UserFriendlyRNG
File "/scratch/sage-4.7.1.rc1/local/lib/python/site-packages/Crypto/
Random/_UserFriendlyRNG.py", line 33, in <module>
from math import floor
ImportError: cannot import name floor
Kiran
On Jul 25, 6:03 am, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.rc1.
>
> Source archive:
>
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.rc1/sage-4.7...
> The source and upgrade path can also be found on the mirror network
> (you might need to wait a while before the mirrors are synchronized):
>
> http://www.sagemath.org/download-latest.html
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
>
> == Tickets ==
>
> * We closed 202 tickets in this release. For details, see
>
Volker Braun
I got a bunch of import failures (this is 64-bit Fedora, in case it
matters).
Jeroen Demeyer
If we know precisely which software is needed, we should add it to the
prerequisites check of Sage.
leif
"from math import floor ... ImportError" doesn't sound like that.
Though it doesn't look like Cython was directly involved here, you get
strange import errors in case you set CFLAGS to anything (even to ""),
omitting "-fno-strict-aliasing" from them.
I haven't observed similar for Python packages, i.e. only the Sage
library is affected by that. If that's the case (if you for example
can't start Sage because of similar import errors), simply run
$ (unset CFLAGS ; ./sage -ba-force)
or use the CFLAGS you want, but add "-fno-strict-aliasing" to them:
$ env CFLAGS="$CFLAGS -fno-strict-aliasing" ./sage -ba-force
-leif
amaseam
> On 2011-07-27 14:00, slelievre wrote:
>> - intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
>> testlong fails on interrupt.pyx ("killed by signal 11")
>
> Are you able to give me shell access on such a machine?
Yes, I wrote to you off-list about that.
slelievre
I only tried to build Sage 4.7.1.rc0 and Sage 4.7.1.rc1 on it.
There's no error message, it just seems to take forever on that step,
so I assumed something went wrong and stopped it after a day or so.
Maybe I should let it try for a few days? I should also check if there's
room for more ram and whether that could help finish the build.
kcrisman
On Aug 3, 2:15 am, slelievre <samuel.lelie...@gmail.com> wrote:
> 2011/7/29 kcrisman <kcris...@gmail.com>:
machine with just 512 MB RAM.
One thing you can try is to cancel the build, then just type make
again. But strange if this is repeatable.
Jeroen Demeyer
> 2011/7/28 Jeroen Demeyer <jdem...@cage.ugent.be>:
>> On 2011-07-27 14:00, slelievre wrote:
>>> - intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
>>> testlong fails on interrupt.pyx ("killed by signal 11")
>>
>> Are you able to give me shell access on such a machine?
I have compiled Sage 4.7.1 (identical to rc1) on that machine and
*cannot* reproduce the problem. make ptestlong simply succeeds. I also
did 10 times
./sage -t -long devel/sage/sage/tests/interrupt.pyx
and it worked.
Jeroen.
Kiran Kedlaya
no problem, so there may be something more subtle going on.
One issue is that this machine is still on FC 10. It is sufficiently
old that it is likely to be replaced (by the end of the year) rather
than upgraded.
Kiran
Jeroen Demeyer
> - intel Mac, Mac OS X 10.6.8, XCode 3.2.6, gcc 4.2.1:
> testlong fails on interrupt.pyx ("killed by signal 11")
Could it be that the problem only happens when the machine is busy and
the issue is not Sage but something external (like out of memory...)?
Francois Bissey
> On Mon, 25 Jul 2011 20:52:59 john. hoebing wrote:
> > Here's Ubuntu 11.10 alpha2 updated with the latest gcc-4.6.1
> > as of today, compiling sage-4.7.1.rc1:
> >
> > ...
> > /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> > symbol 'dlclose@@GLIBC_2.2.5'
> > /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> > x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> > /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> > operation
> > collect2: ld returned 1 exit status
> > make[4]: *** [iparith.inc] Error 1
> > make[4]: *** Waiting for unfinished jobs....
> > /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> > symbol 'dlclose@@GLIBC_2.2.5'
> > /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> > x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> > /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> > operation
> > collect2: ld returned 1 exit status
> > ...
And I forgot, do you have the file:
/usr/lib/x86_64-linux-gnu/libdl.so
or possibly
/usr/lib64/x86_64-linux-gnu/libdl.so
on your system? If not, finding .deb providing it would be a start.
Francois
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
Francois Bissey
> Here's Ubuntu 11.10 alpha2 updated with the latest gcc-4.6.1
> as of today, compiling sage-4.7.1.rc1:
>
> ...
> /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> symbol 'dlclose@@GLIBC_2.2.5'
> /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> operation
> collect2: ld returned 1 exit status
> make[4]: *** [iparith.inc] Error 1
> make[4]: *** Waiting for unfinished jobs....
> /usr/bin/ld: ../kernel/libkernel.a(mod_raw.o): undefined reference to
> symbol 'dlclose@@GLIBC_2.2.5'
> /usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/
> x86_64-linux-gnu/libdl.so so try adding it to the linker command line
> /usr/lib/x86_64-linux-gnu/libdl.so: could not read symbols: Invalid
> operation
> collect2: ld returned 1 exit status
> ...
>
>
> $ gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/
> 4.6.1/lto-wrapper
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
> 4.6.1-5ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.6/
> README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/
> usr --program-suffix=-4.6 --enable-shared --enable-multiarch --with-
> multiarch-defaults=x86_64-linux-gnu --enable-linker-build-id --with-
> system-zlib --libexecdir=/usr/lib/x86_64-linux-gnu --without-included-
> gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/
> 4.6 --libdir=/usr/lib/x86_64-linux-gnu --enable-nls --with-sysroot=/ --
> enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-
> time=yes --enable-plugin --enable-objc-gc --disable-werror --with-
> arch-32=i686 --with-tune=generic --enable-checking=release --
> build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-
> gnu
> Thread model: posix
> gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-5ubuntu2)
> $
> ...
>
> I don't know if anyone is claiming that gcc-4.6.1 is supposed to
> build sage, but in any case it doesn't build it on the oneiric alpha2
> release as of today.
you should precise that the failure is in building singular [says he who has
spend too much on it and can recognize file names immediately]. Just tell us
if I am wrong.