Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi all, I tried sage -ba and the build now completes. Sage now starts without errors! So it looks to me like the patch to module_list.py is needed for openSUSE 11.2. Thanks, all. I also ran: ./sage -docbuild all html 21 | tee -a dochtml.log It also looks like that works fine now, too. I am now seeing an error message when starting the sage notebook - see below. If I display http://localhost:8000 instead of http://localhost:8000/?startup_token=ae62addaf110060a2765c595ea17d16 the notebook works OK. Best, Paul ./sage -notebook -- | Sage Version 4.4.1, Release Date: 2010-05-02 | | Type notebook() for the GUI, and license() for information.| -- Please wait while the Sage Notebook server starts... ... The notebook files are stored in: sage_notebook.sagenb ** ** * Open your web browser to http://localhost:8000 * ** ** 2010-05-21 01:03:09+1000 [-] Log opened. 2010-05-21 01:03:09+1000 [-] twistd 9.0.0 (/home/leopardi/src/Sage/sage-4.4.1/local/bin/python 2.6.4) starting up. 2010-05-21 01:03:09+1000 [-] reactor class: twisted.internet.selectreactor.SelectReactor. 2010-05-21 01:03:09+1000 [-] twisted.web2.channel.http.HTTPFactory starting on 8000 2010-05-21 01:03:09+1000 [-] Starting factory twisted.web2.channel.http.HTTPFactory instance at 0x3e25ab8 unknown program name(24368)/ ClientApp::doIt: Creating ClientApp kioclient(24368) ClientApp::kde_open: KUrl(http://localhost:8000/?startup_token=ae62addaf110060a2765c595ea17d16;) kioclient(24368)/kdecore (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-leopardi/ksycoca4 kioclient(24368) KSharedUiServerProxy::KSharedUiServerProxy: kuiserver registered 2010-05-21 01:03:16+1000 [HTTPChannel,1,127.0.0.1] /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/twisted/internet/defer.py:262: exceptions.DeprecationWarning: Don't pass strings (like 'Bad token') to failure.Failure (replacing with a DefaultException). 2010-05-21 01:03:16+1000 [HTTPChannel,1,127.0.0.1] Exception rendering: 2010-05-21 01:03:16+1000 [HTTPChannel,1,127.0.0.1] Unhandled Error Traceback (most recent call last): Failure: twisted.python.failure.DefaultException: Bad token -- 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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks Nathan, Mike, I applied http://trac.sagemath.org/sage_trac/attachment/ticket/8844/trac_8844- module_list.patch to $SAGE_ROOT/devel/sage-main/module_list.py. What do I now need to do to re-build sage without starting from scratch? sage -b and sage -f sage seem to work, but they don't fix the unresolved symbols problem. Is there a standard procedure for patching that I am missing here? I don't see anything relevant in http://www.sagemath.org/doc/developer/producing_patches.html Best, Paul -- 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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi all, OK. I have now run make again, this time with unset SAGE_CHECK unset SAGE64 The build apparently completes, but dochtml.log still has much the same error messages: --- sphinx-build -b html -d /home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/doctrees/en/numerical_sage /home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/en/numerical_sage /home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/html/en/numerical_sage Traceback (most recent call last): File /home/leopardi/src/Sage/sage-4.4.1/local/bin/sphinx-build, line 6, in module import sage.all File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/all.py, line 72, in module from sage.rings.all import * File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/all.py, line 65, in module from finite_rings.all import * File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/finite_rings/all.py, line 21, in module from constructor import (FiniteField, is_FiniteField, is_PrimeFiniteField, File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/finite_rings/constructor.py, line 162, in module import sage.rings.polynomial.polynomial_element as polynomial_element File polynomial_element.pyx, line 33, in init sage.rings.polynomial.polynomial_element (sage/rings/polynomial/polynomial_element.c:42238) File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/polynomial/polynomial_ring.py, line 105, in module import sage.rings.polynomial.polynomial_element_generic as polynomial_element_generic File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/polynomial/polynomial_element_generic.py, line 37, in module from sage.rings.polynomial.polynomial_ring_constructor import PolynomialRing File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/polynomial/polynomial_ring_constructor.py, line 41, in module import sage.rings.padics.padic_base_leaves as padic_base_leaves File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/padics/padic_base_leaves.py, line 189, in module from padic_capped_relative_element import pAdicCappedRelativeElement File padic_capped_relative_element.pyx, line 1, in init sage.rings.padics.padic_capped_relative_element (sage/rings/padics/padic_capped_relative_element.c:17903) ImportError: /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/padics/padic_base_generic_element.so: undefined symbol: __gmpz_cmp Build finished. The built documents can be found in /home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/html/en/numerical_sage [...] --- Running sage still results in: --- ./sage -- | Sage Version 4.4.1, Release Date: 2010-05-02 | | Type notebook() for the GUI, and license() for information.| -- --- ImportError Traceback (most recent call last) /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/IPython/ipmaker.pyc in force_import(modname) 64 reload(sys.modules[modname]) 65 else: --- 66 __import__(modname) 67 68 /home/leopardi/src/Sage/sage-4.4.1/local/bin/ipy_profile_sage.py in module() 5 preparser(True) 6 7 import sage.all_cmdline 8 sage.all_cmdline._init_cmdline(globals()) 9 /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/all_cmdline.py in module() 12 try: 13 --- 14 from sage.all import * 15 from sage.calculus.predefined import x 16 preparser(on=True) /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/all.py in module() 70 get_sigs() 71 --- 72 from sage.rings.all import * 73 from sage.matrix.all import * 74 /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/all.py in module() 63 64 # Finite fields --- 65 from finite_rings.all import * 66 67 # Number field /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/finite_rings/all.py in module() 19 #* 20 --- 21 from constructor import (FiniteField, is_FiniteField, is_PrimeFiniteField, 22 conway_polynomial, exists_conway_polynomial) 23 GF = FiniteField /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site- packages/sage/rings/finite_rings/constructor.py in module() 160 import sage.rings.integer as
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi all,
The build on my machine apparently finished. The end of install.log looks
like:
--
[...]
Successfully installed sagetex-2.2.5
Running the test suite.
pdfTeX using libpoppler 3.1415926-1.40.9-2.2 (Web2C 7.5.7)
kpathsea version 3.5.7
Copyright 2008 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Kpathsea is copyright 2008 Karl Berry and Olaf Weber.
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX using libpoppler copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX using libpoppler source.
Primary author of pdfTeX using libpoppler: Peter Breitenlohner (eTeX)/Han The
Thanh (pdfTeX).
Kpathsea written by Karl Berry, Olaf Weber, and others.
Compiled with libpng 1.2.39; using libpng 1.2.35
Compiled with zlib 1.2.3; using zlib 1.2.3
Compiled with xpdf version 3.01
Could not find tkz-berge.sty. Skipping test of SageTeX spkg.
Now cleaning up tmp files.
Making Sage/Python scripts relocatable...
Making script relocatable
Finished installing sagetex-2.2.5.spkg
make[1]: Leaving directory `/home/leopardi/src/Sage/sage-4.4.1/spkg'
real147m46.260s
user98m19.883s
sys 8m39.355s
To install gap, gp, singular, etc., scripts
in a standard bin directory, start sage and
type something like
sage: install_scripts('/usr/local/bin')
at the Sage command prompt.
To build the documentation, run
make doc
Sage build/upgrade complete!
--
The make script then apparently ran the command:
./sage -docbuild all html 21 | tee -a dochtml.log
The start of dochtml.log looks like:
--
python: can't open file
'/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/common/builder.py': [Errno
2] No such file or directory
python: can't open file
'/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/common/builder.py': [Errno
2] No such file or directory
sphinx-build -b html -d
/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/doctrees/en/numerical_sage
/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/en/numerical_sage
/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/html/en/numerical_sage
Traceback (most recent call last):
File /home/leopardi/src/Sage/sage-4.4.1/local/bin/sphinx-build, line 6, in
module
import sage.all
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/all.py, line 72, in module
from sage.rings.all import *
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/all.py, line 65, in module
from finite_rings.all import *
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/finite_rings/all.py, line 21, in module
from constructor import (FiniteField, is_FiniteField, is_PrimeFiniteField,
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/finite_rings/constructor.py, line 162, in module
import sage.rings.polynomial.polynomial_element as polynomial_element
File polynomial_element.pyx, line 33, in init
sage.rings.polynomial.polynomial_element
(sage/rings/polynomial/polynomial_element.c:42238)
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/polynomial/polynomial_ring.py, line 105, in module
import sage.rings.polynomial.polynomial_element_generic as
polynomial_element_generic
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/polynomial/polynomial_element_generic.py, line 37, in
module
from sage.rings.polynomial.polynomial_ring_constructor import
PolynomialRing
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/polynomial/polynomial_ring_constructor.py, line 41, in
module
import sage.rings.padics.padic_base_leaves as padic_base_leaves
File /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/padics/padic_base_leaves.py, line 189, in module
from padic_capped_relative_element import pAdicCappedRelativeElement
File padic_capped_relative_element.pyx, line 1, in init
sage.rings.padics.padic_capped_relative_element
(sage/rings/padics/padic_capped_relative_element.c:17903)
ImportError: /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-
packages/sage/rings/padics/padic_base_generic_element.so: undefined symbol:
__gmpz_cmp
Build finished. The built documents can be found in
/home/leopardi/src/Sage/sage-4.4.1/devel/sage/doc/output/html/en/numerical_sage
[...]
--
The ./sage script exists, but when I run it, Sage outputs the following:
--
leopa...@linfinit:~/src/Sage/sage-4.4.1 ./sage
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks, Jaap, From: Jaap Spies j.sp...@hccnet.nl Mon, 17 May 2010 18:30:23 +0200 Paul Leopardi wrote: Thanks, Georg, I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5, used tar zcf to creat a replacement spkg, and the make now continues past symmetrica-2.0.p5. The make is still running. I have the following environment variables defined: SAGE64=yes SAGE_CHECK=yes Don't do this! SAGE64=yes is reserved for building 64 bit on OSX and (Open) Solaris! Don't set SAGE_CHECK unless you know what you are doing. SAGE64=yes: I did this because Georg S. Weber suggested it (on this thread). Where is the SAGE64 environment variable documented? In local/bin/sage-env it says: echo SAGE64 Set to \yes\ to build a 64-bit binary (Solaris SPARC or Solaris x86 only) and does not mention OSX. SAGE_CHECK=yes: I did this because it is mentioned in point 3 of README.txt: If you want to run the test suite for each individual spkg as it is installed, type export SAGE_CHECK=yes before starting the Sage build. This will run each test suite and will raise an error if any failures occur. Should there be a trac ticket to update README.txt to say: Don't set SAGE_CHECK unless you know what you are doing. See http://groups.google.com/group/sage- devel/browse_thread/thread/c27cbd64eb0e2534 Ticket #6282 asked for SAGE_CHECK to be documented and gave the existing wording in README.txt Ticket #8806 asked for README.txt to be updated, but did not mention SAGE_CHECK. Ticket #8106 asked for the documentation of SAGE_CHECK in README.txt to be changed along the lines above, but I can't find any relevant changes in http://hg.sagemath.org Should I be able to find changes to README.txt somewhere in there? Bottom line: I am now doing this in my sage-4.4.1 directory (using the fixed libreadline and symmetrica spkg files instead of the downloaded ones) unset SAGE_CHECK unset SAGE64 make clean make We shall see what happens. Best, Paul -- 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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi all,
make clean
make
does not work the way I expected it to. I expected it to clean out my existing
build of sage and start again. Instead, make clean outputs:
echo Deleted spkg/build
Deleted spkg/build
rm -rf spkg/build
mkdir -p spkg/build
echo Deleted spkg/archive
Deleted spkg/archive
rm -rf spkg/archive
mkdir -p spkg/archive
and make outputs:
cd spkg ./install all 21 | tee -a ../install.log
make[1]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg'
sage-spkg sagenb-0.8.p1 21
Warning: Attempted to overwrite SAGE_ROOT environment variable
sagenb-0.8.p1
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: sagenb-0.8.p1 is already installed
cd /home/leopardi/src/Sage/sage-4.4.1 . local/bin/sage-env cd local/bin/
./sage-make_relative
Making script relocatable
sage-spkg sage-4.4.1
Warning: Attempted to overwrite SAGE_ROOT environment variable
sage-4.4.1
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: sage-4.4.1 is already installed
cd /home/leopardi/src/Sage/sage-4.4.1 . local/bin/sage-env cd local/bin/
./sage-make_relative
Making script relocatable
sage-spkg gap-4.4.12.p3 21
Warning: Attempted to overwrite SAGE_ROOT environment variable
gap-4.4.12.p3
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: gap-4.4.12.p3 is already installed
make[1]: Leaving directory `/home/leopardi/src/Sage/sage-4.4.1/spkg'
real0m1.833s
user0m0.321s
sys 0m0.364s
To install gap, gp, singular, etc., scripts
in a standard bin directory, start sage and
type something like
sage: install_scripts('/usr/local/bin')
at the Sage command prompt.
To build the documentation, run
make doc
Sage build/upgrade complete!
./sage -docbuild all html 21 | tee -a dochtml.log
I am now going to start the build from scratch (using the fixed libreadline
and symmetrica spkg files instead of the downloaded ones).
Best, Paul
--
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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
On Mon, May 17, 2010 at 4:22 PM, Paul Leopardi
paul.leopa...@iinet.net.au wrote:
Hi all,
make clean
make
does not work the way I expected it to. I expected it to clean out my existing
build of sage and start again. Instead, make clean outputs:
Use make distclean.
William
echo Deleted spkg/build
Deleted spkg/build
rm -rf spkg/build
mkdir -p spkg/build
echo Deleted spkg/archive
Deleted spkg/archive
rm -rf spkg/archive
mkdir -p spkg/archive
and make outputs:
cd spkg ./install all 21 | tee -a ../install.log
make[1]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg'
sage-spkg sagenb-0.8.p1 21
Warning: Attempted to overwrite SAGE_ROOT environment variable
sagenb-0.8.p1
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: sagenb-0.8.p1 is already installed
cd /home/leopardi/src/Sage/sage-4.4.1 . local/bin/sage-env cd local/bin/
./sage-make_relative
Making script relocatable
sage-spkg sage-4.4.1
Warning: Attempted to overwrite SAGE_ROOT environment variable
sage-4.4.1
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: sage-4.4.1 is already installed
cd /home/leopardi/src/Sage/sage-4.4.1 . local/bin/sage-env cd local/bin/
./sage-make_relative
Making script relocatable
sage-spkg gap-4.4.12.p3 21
Warning: Attempted to overwrite SAGE_ROOT environment variable
gap-4.4.12.p3
Machine:
Linux linfinit 2.6.31.12-0.1-default #1 SMP PREEMPT 2010-03-16 21:25:39 +0100
x86_64 x86_64 x86_64 GNU/Linux
sage: gap-4.4.12.p3 is already installed
make[1]: Leaving directory `/home/leopardi/src/Sage/sage-4.4.1/spkg'
real 0m1.833s
user 0m0.321s
sys 0m0.364s
To install gap, gp, singular, etc., scripts
in a standard bin directory, start sage and
type something like
sage: install_scripts('/usr/local/bin')
at the Sage command prompt.
To build the documentation, run
make doc
Sage build/upgrade complete!
./sage -docbuild all html 21 | tee -a dochtml.log
I am now going to start the build from scratch (using the fixed libreadline
and symmetrica spkg files instead of the downloaded ones).
Best, Paul
--
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
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
On 05/16/10 07:01 AM, Paul Leopardi wrote: Hi all, I am trying to build Sage 4.4.1 from sourece, using gcc 4.4.1 on SUSE 11.2. So far I have had two failures. I can work around the first, but have no clue about the second. Best, Paul 1. Problem with libreadline Symptom: [...]/local/lib/libreadline.so.6: undefined symbol: PC Workaround: Try to use native librealine. leopa...@linfinit:~/src/sage/sage-4.4.1 ls -l local/lib/libread* lrwxrwxrwx 1 leopardi users 24 2010-05-16 12:37 local/lib/libreadline.a - /usr/lib64/libreadline.a lrwxrwxrwx 1 leopardi users 16 2010-05-16 12:33 local/lib/libreadline.so - libreadline.so.6 lrwxrwxrwx 1 leopardi users 18 2010-05-16 12:35 local/lib/libreadline.so.6 - libreadline.so.6.0 lrwxrwxrwx 1 leopardi users 25 2010-05-16 12:36 local/lib/libreadline.so.6.0 - /lib64/libreadline.so.6.0 There is something strange about readline on OpenSUSE. There some code which does something different on OpenSUSE to other platforms. Perhaps that is not working correctly. It looks a bit of a hack if I'm honest. I don't have time to look at it now, but if you find the readline-$version.spkg, you will find there is something in there which checks a header file and makes a decision based on the header file. It may be that the test does not work on OpenSUSE 11.2. 2. Problem with symmetrica Symptom: /bin/bash: symbol lookup error: [...]/spkg/build/symmetrica-2.0.p5/src/nb.c:4087: undefined reference to `cos' Workaround: ??? Perhaps it needs the maths library linked, -lm, as that is where 'cos' will be. Though that seems a strange thing to be missing. Extracts from install.log: 1. Problem with libreadline readline.c:1112: warning: ‘reset_default_bindings’ defined but not used This, and the tons of other warnings worries me. search.c: In function ‘_rl_nsearch_init’: search.c:213: warning: too many arguments for format How the hell do the developers let that get by? What the where they thinking to ignore such a warning? complete.c: In function ‘fnwidth’: complete.c:643: warning: implicit declaration of function ‘wcwidth’ That probably needs #include wchar.h added to a source file. ../search.c: In function ‘_rl_nsearch_init’: ../search.c:213: warning: too many arguments for format IMHO, it would be better if compilers would throw this as an error. /bin/bash: symbol lookup error: /home/leopardi/src/sage/sage-4.4.1/local/lib/libreadline.so.6: undefined symbol: PC Successfully installed readline-6.0.p1 So readline installs, despite the fact the code looks as though it could do with a major cleanup to me. It is clearly is the cause of many later problems. sage: An error occurred while installing sqlite-3.6.22 sqlite is a well tested bit of code. The developers take testing very seriously - see http://www.sqlite.org/testing.html sage: An error occurred while installing symmetrica-2.0.p5 I would look over the readline.spkg and see if there are any clues there. I think you will find some SUSE specific code there, which may just not work. 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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks for the help. I tried again but with export SAGE64=yes before running make. The only difference is that the calls to gcc now include the option -m64. The warning and error messages are the same. Best, Paul --- install.2.log 2010-05-16 15:38:19.0 +1000 +++ install.log 2010-05-16 23:34:28.0 +1000 @@ -1,110348 +1,4 @@ make[1]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg' -sage-spkg sqlite-3.6.22 21 [...] -Finished installing singular-3-1-0-4-20100214.spkg sage-spkg symmetrica-2.0.p5 21 Warning: Attempted to overwrite SAGE_ROOT environment variable symmetrica-2.0.p5 @@ -110576,76 +232,76 @@ gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) make[2]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg/build/symmetrica-2.0.p5/src' -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bar.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bi.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE boe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bruch.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE classical.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE de.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE di.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ff.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE galois.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ga.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE gra.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE hash.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE hiccup.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE io.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ko.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE list.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE lo.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ma.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mee.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mem.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mes.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhp.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhs.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mmm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mms.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mod_dg_sbd.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bar.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bi.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE boe.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bruch.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE classical.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE de.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE di.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ff.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE galois.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ga.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE gra.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE hash.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE hiccup.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE io.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ko.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE list.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE lo.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ma.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mee.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mem.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mes.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhe.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhh.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhm.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhp.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhs.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mmm.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mms.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mod_dg_sbd.c mod_dg_sbd.c: In function ‘embedding_mod_into_ord’: mod_dg_sbd.c:624: warning: passing argument 4 of ‘qsort’ from incompatible pointer type /usr/include/stdlib.h:710: note: expected ‘__compar_fn_t’ but argument is of type ‘INT (*)()’ -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mo.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mpp.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mps.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mse.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE msh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE msm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mss.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE muir.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE na.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nb.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nc.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nu.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE part.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pee.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE peh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pem.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE perm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pes.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phs.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE plet.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pme.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pmh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE poly.c -gcc -c -O1 -fPIC -g
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks, Georg, I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5, used tar zcf to creat a replacement spkg, and the make now continues past symmetrica-2.0.p5. The make is still running. I have the following environment variables defined: SAGE64=yes SAGE_CHECK=yes SAGE_ROOT= Best, Paul -- 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
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
In the makefile for symmetrica, the -lm has to go after all the .o files that need libm.a or libm.so. This is standard practice for GNU binutils and not a quirk of OpenSUSE, so I don't see why the build should have worked with any other Linux distribution (remember that I have exported SAGE_CHECK=yes ). In the GNU binutils doc under options: http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options -l namespec --library=namespec Add the archive or object file specified by namespec to the list of files to link. This option may be used any number of times. If namespec is of the form :filename, ld will search the library path for a file called filename, otherwise it will search the library path for a file called libnamespec.a. On systems which support shared libraries, ld may also search for files other than libnamespec.a. Specifically, on ELF and SunOS systems, ld will search a directory for a library called libnamespec.so before searching for one called libnamespec.a. (By convention, a .so extension indicates a shared library.) Note that this behavior does not apply to :filename, which always specifies a file called filename. The linker will search an archive only once, at the location where it is specified on the command line. If the archive defines a symbol which was undefined in some object which appeared before the archive on the command line, the linker will include the appropriate file(s) from the archive. However, an undefined symbol in an object appearing later on the command line will not cause the linker to search the archive again. See the -( option for a way to force the linker to search archives multiple times. You may list the same archive multiple times on the command line. This type of archive searching is standard for Unix linkers. However, if you are using ld on AIX, note that it is different from the behaviour of the AIX linker. -- 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
