Hi Ondrej, On Tue, Sep 1, 2009 at 4:01 AM, Ondrej Certik<ond...@certik.cz> wrote: > > Hi, > > we got this bugreport in femhub: > > http://groups.google.com/group/femhub/browse_thread/thread/1bfad9ea3ec7df48 > > and it turns out it is a Sage problem as well. > > Essentially if the user installs his own python and puts it into PATH, > Sage picks this python instead (and then it fails of course, due to > slight incompatibilities among python versions, like UTF). I don't > have time right now to debug it.
Sage 4.1.1 is known to fail to compile on the following versions of SUSE: * SUSE Linux Enterprise Server 10 SP1 ia64 with GCC 4.4.1. The build process dies very early when it tries to build bzip2-1.0.5. * openSUSE 11.1 x86_64 with GCC 4.4.1. In this case, the build fails because cliquer-1.2 is known to fail to build on some 64-bit platforms. Other reported platforms under which Sage 4.1.1 fails to compile include Mac OS X 10.5.8 compile in 64-bit mode (see #6681), Fedora 10 64-bit (fail due to cliquer, see #6746), and Xubuntu 9.04 32-bit on an IBM Thinkpad T43 with Centrino 1.86 Ghz and 1.5 GB RAM; see this sage-devel thread: http://groups.google.com/group/sage-devel/browse_thread/thread/64ee480aaef342da Where the compilation fails under SUSE, there is a system-wide installation of Python and the PATH is not prepended with absolute paths to any installation of Python. So if Sage 4.1.1 fails to build because of cliquer, this is a 32- versus 64-bit issue in cliquer itself. -- Regards Minh Van Nguyen --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
