On 8 June 2010 17:17, Matthew Gwynne <mathew.gwy...@gmail.com> wrote: > Hi, > > As some additional points of interest/questions for this problem: > > 1. Version 2.7.2 was the last Sage version which could be installed. > We tried most versions since then (latest 4.4.2), and they all failed > with the same error.
Looking at the error message: ----------------------------------------- /usr/local/lib/../lib/libstdc++.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[4]: *** [libfplll.la] Error 1 ----------------------------------------- it rather suggests the compiler is complaining about a file in /usr/local, rather than one in the Sage directory. It's quite possible that libfplll is the first package to link to the C++ library, which is what that file is. I would consider downloading gcc 4.4.4 (not 4.5, as that is quite new, and probably more buggy than the 4.4 series), and compiling that. You would also need to download mpfr and gmp, and build those. It's difficult to suggest much more. I'm not a linux guru, but had I hit the same message on the Solaris operating system, I would suspect the compiler. (Not that I claim to be a Solaris guru!) It's clear different parts of your compiler were built at different times, as your C and C++ compilers were built without Fortran support, and the Fortran compiler was built with C, C++ and Fortran support. That in itself should not stop the combination working, but I'd certainly look at trying another compiler. > 2. It is always the same package which fails. We don't have any other > installation problems in our system, so we wonder if that package > might be faulty in some way? Is there some difference with that > package compared to other packages (in the Sage-build)? To be honest, few packages are configured identically. > 3. Is that package needed? Is there some way we can prevent it from > being used/built? You can stop pacakge 'foobar' building by fooling Sage into believing the package is already installed. The way to do that is touch spkg/installed/foobar In the case of some packages, that will still allow Sage to build, but certainly not all packages. I don't know for sure whether this would be essential or not to get some sort of working Sage. It would be useful to try this. You might find other packages fail with a similar error, which would make me even more suspicious it is a compiler problem. > Thanks again! > > Matthew Sorry I can't be of much more help. Dave > > On May 26, 2:54 pm, David Kirkby <david.kir...@onetel.net> wrote: >> On 26 May 2010 11:57, Matthew Gwynne <mathew.gwy...@gmail.com> wrote: >> >> >> >> >> >> > Hi, >> >> > The system information is given below - >> >> > **************************************************** >> > Host system >> > uname -a: >> > Linux cs-wsok 2.6.13-15.8-smp #1 SMP Tue Feb 7 11:07:24 UTC 2006 >> > x86_64 x86_64 x86_64 GNU/Linux >> > **************************************************** >> > **************************************************** >> > CC Version >> > gcc -v >> > Using built-in specs. >> > Target: x86_64-unknown-linux-gnu >> > Configured with: ./configure --enable-languages=c,c++ --enable- >> > threads=posix --enable-shared >> > Thread model: posix >> >> Something is odd here. You need to have a compiler supporting Fortran, >> yet yours was compiled without Fortran support. I'm very surprised the >> 'prereq' script does not detect this, as it should check for a fortran >> compiler and confirm its the same version as the C and C++ compilers. >> >> So unless you have two installations of gcc, both of the same version, >> I don't know how you got this far. >> >> can you give me the outputs of >> >> $ command -v gcc >> $ command -v g++ >> $ command -v gfortran >> $ gcc -v >> $ g++ -v >> $ gfortran -v >> $ echo $LD_LIBRARY_PATH >> $ echo $CC >> $ echo $CXX >> $ echo SAGE_FORTRAN >> $ echo SAGE_FORTRAN_LIB >> >> Specifying the compiler locations with CC and CXX does not work too well >> >> 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 > -- 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
