On 30 November 2010 09:12, Jean-Pierre Flori <[email protected]> wrote: > > > On 30 nov, 00:34, David Kirkby <[email protected]> wrote: >> On 29 November 2010 14:49, Jean-Pierre Flori <[email protected]> wrote: >> >> > It now fails when building sqlite: >> >> > /usr/local/gcc4/bin/gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME= >> >> how are you getting Sage to build with a gcc in /usr/local/gcc4/bin/ ? >> >> If you are doing what seems a logical thing to do (set the CC >> variable), then I'm afraid to say this does not work reliably. Many >> parts of Sage will ignore CC. You *must* make sure the first gcc in >> your path is >= 4.0.1. >> > I set GG to /usr/local/gcc4/bin/gcc (and CXX...), but also prepended / > usr/local/gcc4/bin to PATH and /usr/local/gcc4/lib to LD_LIBRARY_PATH > because of the warnings in the installation guide. > I set SAGE_FORTRAN and SAGE_FORTRAN_LIB to correct values and copied > gtar and gmake to tar and make in a custom directory prepended to PATH
I would suggest you unset CC and CXX. Sage certainly builds without them. Setting them works in some places, and does not in others, so there's nothing to be gained by setting them really. I doubt that's the problem here. >> Can you give me the output of >> >> 1) $ command -v gcc >> 2) $ gcc --version >> > <fl...@infres2: 510> gcc -v > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/local/packages/gcc4_10/libexec/gcc/sparc-sun- > solaris2.10/4.5.1/lto-wrapper > Target: sparc-sun-solaris2.10 > Configured with: ../configure --prefix=/usr/local/packages/gcc4_10 -- > with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable- > languages=c,c++,fortran,objc,java > Thread model: posix > gcc version 4.5.1 (GCC) > <fl...@infres2: 511> command -v gcc > /usr/local/gcc4/bin/gcc That looks mostly OK. However, I note that gcc was configured using ./configure rather than /[patch/to/configure In practice, I don't know if that can screw gcc up, but it is specifically recommended NOT to do this: http://gcc.gnu.org/install/configure.html "First, we *highly* recommend that GCC be built into a separate directory from the sources which does *not* reside within the source tree." But your gcc was built in a way that is highly recommended not to do so. When I run gcc --v, I see: Configured with: ../gcc-4.5.0/configure which is the way gcc is supposed to be built. I can try building Sage with gcc 4.5.1, since we have not used 4.5.1 anywere, but we have used 4.5.0 and it builds fine. I just stated a build on a Sun Blade 1000 running the very first release of Solaris 10 (March 2005). The build has not completed, but sqlite has built ok. You might want to build gmp, mpfr, mpc and gcc using the gcc is /usr/sfw/bin. I believe your system admin has not done this properly, but I must admit, I doubt that is the cause. Dave Dave -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
