[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-20 Thread Georg S. Weber
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 displayhttp://localhost:8000instead ofhttp://localhost:8000/?startup_token=ae62addaf110060a2765c595ea17d16 the notebook works OK. Best, Paul Thank you very

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Nathan O'Treally
On 18 Mai, 14:48, Paul Leopardi paul.leopa...@iinet.net.au wrote: 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

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Nathan O'Treally
On 19 Mai, 22:59, Nathan O'Treally not.rea...@online.de wrote: On 18 Mai, 14:48, Paul Leopardi paul.leopa...@iinet.net.au wrote: (sage/rings/padics/padic_capped_relative_element.c:17903) ImportError: /home/leopardi/src/Sage/sage-4.4.1/local/lib/python2.6/site-

Re: [sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Mike Hansen
On Wed, May 19, 2010 at 2:19 PM, Nathan O'Treally not.rea...@online.de wrote: __gmpz_cmp is just the *first* symbol (from libgmp) that can't be resolved. (The reason this though works on other systems is just how/where the linker looks for unresolved symbols, i.e.

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Nathan O'Treally
On 19 Mai, 23:22, Mike Hansen mhan...@gmail.com wrote: On Wed, May 19, 2010 at 2:19 PM, Nathan O'Treally not.rea...@online.de wrote: __gmpz_cmp is just the *first* symbol (from libgmp) that can't be resolved. (The reason this though works on other systems is just how/where the linker

Re: [sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Mike Hansen
On Wed, May 19, 2010 at 2:55 PM, Nathan O'Treally not.rea...@online.de wrote: Mike, could you update the ticket description etc. (to cover Fedora et al.)? (component currently is cygwin.) Sure. P.S. I thought some clib ... declaration in the .pyx/.pxi files would do it... Yes, that would

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-19 Thread Nathan O'Treally
On 20 Mai, 02:59, Paul Leopardi paul.leopa...@iinet.net.au wrote: Thanks Nathan, Mike, I appliedhttp://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

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-17 Thread Jaap Spies
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

Re: [sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-17 Thread Dr. David Kirkby
On 05/17/10 05:30 PM, Jaap Spies wrote: 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

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-16 Thread Georg S. Weber
Hi, these are two (if not three) very different kinds of problems. 1. The readline story on OpenSuse 11.1, 11.2, ArchLinux with Sage Looking at what was done for OpenSuse 11.1 64bit: http://trac.sagemath.org/sage_trac/ticket/4946 and/or for ArchLinux

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-16 Thread Georg S. Weber
Sorry for replying to myself, but I just found this in the current readline spkg's install script: ... if [ -f /etc/SuSE-release ]; then if [ `grep 11.1 /etc/SuSE-release /dev/null; echo $?` -eq 0 ]; then echo OpenSUSE 11.1 detected if [ -d /usr/include/readline/ ]; then

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-16 Thread Nathan O'Treally
On 16 Mai, 14:37, Georg S. Weber georgswe...@googlemail.com wrote: 2. Symmetrica Having a look at an install log of a successful build of the Symmetrica spkg shows that some of the warnings are to be expected, some not. From the logs (gcc -v Using built-in specs. Target: x86_64- suse-linux

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-16 Thread Georg S. Weber
Well, one last try, before I give up. You should have a (temporary) directory /home/leopardi/src/Sage/sage-4.4.1/spkg/build/ symmetrica-2.0.p5/. In its subdirectory src/ there is a file makefile. Change its last line (line 12) from $(CC) $(CFLAGS) -lm test.c bar.o bi.o boe.o bruch.o

Re: [sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

2010-05-16 Thread Minh Nguyen
Hi Georg, On Sun, May 16, 2010 at 10:37 PM, Georg S. Weber georgswe...@googlemail.com wrote: SNIP (do we have OpenSuse 11.2 64bit on the Sage build/test farm?) The build farm of Linux virtual machines has openSUSE 11.1 in 32- and 64-bit versions. The Skynet cluster has 64-bit openSUSE 11.1