[sage-devel] Place .sage directory somewhere other than home?
Hi, We are building sage as part of a development environment which we'd like to be isolated (as much as possible) from the rest of the system, and on which users might have system-wide versions of sage other than the one we installed in this special environment. Is it possible when compiling Sage, or as an option when running it, to force it to always take a particular given directory as the configuration ".sage" directory rather than creating it in the user's home directory? Thanks! Matthew Gwynne -- 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
[sage-devel] Installation of Sage on a Suse 11.0 (x64) system failing
Hi, We are trying to build Sage on a 64-bit OpenSuse 11.0 machine and am getting the following error - gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) Building a 32-bit version of Readline Deleting old readline headers and libs OpenSuSE detected OpenSuSE 11 detected The development version of libreadline is installed -> copying cp: cannot stat `/lib64/libreadline.so.6*': No such file or directory Error copying the system's libreadline sys 0m0.028s sage: An error occurred while installing readline-6.0.p4 despite the fact that readline is installed and Sage suggests it is installing it. Am I missing something? Has anyone seen this before? Also, when posting such things to the list, is there a simple guide somewhere of what information to provide? Perhaps a command one can run in Sage or the build environment to get certain debug information? Thanks in advance! Matthew Gwynne -- 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] Place .sage directory somewhere other than home?
Hi Minh, This is exactly what I was looking for! Thanks! The reason we want to specify a different directory is we have a special Sage installation which we don't want to interfere with the system-wide one. This installation is likely only to be used by a single user (the user who installed our library) and so that shouldn't be a problem. Thanks again! Matthew On Mon, Dec 6, 2010 at 11:25 AM, Minh Nguyen wrote: > Hi Matthew, > > I'm not sure I understand your question correctly, but here goes... > > On Mon, Dec 6, 2010 at 10:09 PM, Matthew Gwynne > wrote: >> Is it possible when compiling Sage, or as an option when running it, >> to force it to always take a particular given directory as the >> configuration ".sage" directory rather than creating it in the user's >> home directory? > > Yes to both when building Sage and when running the (pre)compiled > version. The Sage environment variable you want is DOT_SAGE, which > defaults to the home directory of the user building/running Sage, i.e. > > $HOME/.sage/ > > When compiling Sage, you can set .sage to be a directory other than > $HOME/.sage/. You merely set DOT_SAGE to a directory of your choice > and export that variable. For example, > > $ DOT_SAGE=/tmp//dot_sage/; export DOT_SAGE > > The environment variable DOT_SAGE can in general be used to set the > default directory from which Sage reads in its configuration files > when building/running. To get Sage to by default read configuration > files from another .sage directory, put the above line in your > $HOME/.bashrc or $HOME/.profile. > > For example, my custom build script [1] has these lines: > > if [ -d /tmp/mvngu/dot_sage/ ]; then > rm -rf /tmp/mvngu/dot_sage/ > fi > DOT_SAGE=/tmp/mvngu/dot_sage/; export DOT_SAGE > > and my .bashrc file has these lines: > > if [ `uname -s` = "Linux" ]; then > # The Sage working directory .sage/ > DOT_SAGE=/dev/shm/mvngu/dot_sage; export DOT_SAGE > fi > > I use /tmp and /dev/shm for my .sage directories because those are > fast-ish directories to read from. Sage can take a long time to load, > and I want to speed up the loading as much as I can. > > > [1] http://sage.math.washington.edu/home/mvngu/apps/sageutil/build.sh > > -- > 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 URL: http://www.sagemath.org
[sage-devel] Problems building Sage 4.4.1
Hi, When building Sage 4.4.1, I (and also my colleague) get the following errors during the build process - /bin/sh ./libtool --tag=CXX --mode=link g++ -fPIC -I/home/csoliver/ SAT-Algorithmen/OKplatform/ExternalSources/Installations/Sage/ sage-4.4.1/local/include/ -L/home/csoliver/SAT-Algorithmen/OKplatform/ ExternalSources/Installations/Sage/sage-4.4.1/local/lib -o libfplll.la -rpath /home/csoliver/SAT-Algorithmen/OKplatform/ ExternalSources/Installations/Sage/sage-4.4.1/local/lib -version-info 1:0:1 dummy.lo -lgmp -lmpfr -lmpfr -lgmp -lmpfr -lgmp g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/lib/gcc/ x86_64-unknown-linux-gnu/4.1.2/crtbeginS.o .libs/dummy.o -Wl,--rpath -Wl,/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/ Installations/Sage/sage-4.4.1/local/lib -Wl,--rpath -Wl,/usr/local/ lib/../lib -Wl,--rpath -Wl,/home/csoliver/SAT-Algorithmen/OKplatform/ ExternalSources/Installations/Sage/sage-4.4.1/local/lib -Wl,--rpath - Wl,/usr/local/lib/../lib -L/home/csoliver/SAT-Algorithmen/OKplatform/ ExternalSources/Installations/Sage/sage-4.4.1/local/lib /home/csoliver/ SAT-Algorithmen/OKplatform/ExternalSources/Installations/Sage/ sage-4.4.1/local/lib/libmpfr.so /home/csoliver/SAT-Algorithmen/ OKplatform/ExternalSources/Installations/Sage/sage-4.4.1/local/lib/ libgmp.so -L/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.1.2 -L/usr/ local/lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../x86_64- unknown-linux-gnu/lib -L/usr/local/lib/gcc/x86_64-unknown-linux-gnu/ 4.1.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 /usr/local/ lib/../lib/libstdc++.so -lm -lc -lgcc_s /usr/local/lib/gcc/x86_64- unknown-linux-gnu/4.1.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,- soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.1.0 /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 make[4]: Leaving directory `/home/csoliver/SAT-Algorithmen/OKplatform/ ExternalSources/Installations/Sage/sage-4.4.1/spkg/build/ libfplll-3.0.12.p0/src' Does anyone have any idea if I am doing something wrong, or whether this is a possible problem with Sage itself? Thanks! Matthew -- 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
[sage-devel] Re: Problems building Sage 4.4.1
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 gcc version 4.1.2 My colleague suggest that typically these errors are caused by missing "-fPIC" options when building (or something else must have gone wrong when building the libfpplll library). Thanks! Matthew On May 24, 2:14 pm, kcrisman wrote: > On May 24, 9:11 am, kcrisman wrote: > > > > > > > Dear Matthew, > > > Thanks for your report. I know I can't answer your question fully :) > > but I can say that the most likely way to receive more specific info > > is to also post your OS, chip type if known, and any other info. > > > One reason I say this might be relevant is the following I found doing > > a quick Google search for your error message, > > athttp://ugweb.cs.ualberta.ca/~rod/tutorials/error_messagesC.html: > > > " If you compile part of a > > project on one type of architecture and then try to compile the rest > > of the > > project on another type of architecture, when you go to make the final > > executable the linker/loader will NOT be able to read one of the parts > > of the > > project .o files to create an executable, thus the > > "could not read symbols: File in wrong format" error message." > > > I'm not saying that's what the problem is, but information about your > > physical computer and its system will help enormously in tracking this > > down, especially if others have also experienced it. > > One more possible piece of useful info - any 32 versus 64 bit info you > may have. > > -- > 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 athttp://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
[sage-devel] Re: Problems building Sage 4.4.1
Here is the output: ~> command -v gcc /usr/local/bin/gcc ~> command -v g++ /usr/local/bin/g++ ~> command -v gfortran /usr/local/bin/gfortran ~> 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 gcc version 4.1.2 ~> g++ -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 gcc version 4.1.2 ~> gfortran -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: ./configure --enable-languages=c,c++,fortran --enable- threads=posix --enable-shared Thread model: posix gcc version 4.1.2 ~> echo $LD_LIBRARY_PATH ~> echo $CC ~> echo $CXX ~> echo SAGE_FORTRAN SAGE_FORTRAN ~> echo $SAGE_FORTRAN ~> echo $SAGE_FORTRAN_LIB Thanks! Matthew On May 26, 2:54 pm, David Kirkby wrote: > On 26 May 2010 11:57, Matthew Gwynne 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
[sage-devel] Re: Problems building Sage 4.4.1
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. 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)? 3. Is that package needed? Is there some way we can prevent it from being used/built? Thanks again! Matthew On May 26, 2:54 pm, David Kirkby wrote: > On 26 May 2010 11:57, Matthew Gwynne 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
[sage-devel] Re: Problems building Sage 4.4.1
Thanks for the response! We'll try to disable it for now, and investigate some of the other things mentioned in this thread. The problem we have is that we need to provide something like CC/CXX flags, as the only compiler we can guarantee is the one which we install, which is installed in a specific location, not globally. Is there some way we can do something similar to this in Sage? You said that CC/CXX do not work very well, why is this :(? Thanks! Matthew On Jun 8, 6:21 pm, David Kirkby wrote: > On 8 June 2010 17:17, Matthew Gwynne wrote: > > > Hi, > > > As some additional points of interest/questions for this problem: > > > 1. Version 2.7.2 was the lastSageversion 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 theSagedirectory. 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 theSage-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 foolingSageinto 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 allowSageto build, but > certainly not all packages. I don't know for sure whether this would > be essential or not to get some sort of workingSage. > > 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 wrote: > >> On 26 May 2010 11:57, Matthew Gwynne 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++ > >>
