Hi Michael, The other problem I am facing on powerpc Linux is with compiling with Fortran. Some parts of SAGE accept gfortran and others do not. Here is what I see: checking for Fortran 77 libraries of sage_fortran... checking how to get verbose linking output from gcc -std=gnu99... -v checking for C libraries of gcc -std=gnu99... -L/usr/local/PET/src/ build/sage-2.10.2/local/lib/ -L/usr/local/PET/src/build/sage-2.10.2/ local/lib/../lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2 -L/usr/lib/ gcc/powerpc64-suse-linux/4.1.2/../../../../powerpc64-suse-linux/lib/../ lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib -L/ lib/../lib -L/usr/lib/../lib -L/usr/local/PET/src/build/sage-2.10.2/ local/lib -L/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../ powerpc64-suse-linux/lib -L/usr/lib/gcc/powerpc64-suse-linux/ 4.1.2/../../.. -lgcc_s checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... configure: error: cannot compile a simple Fortran program See `config.log' for more details. Error configuring R.
real 0m57.989s user 0m23.697s sys 0m23.042s sage: An error occurred while installing r-2.6.1.p14 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 and type 'make'. Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" in order to set all environment variables correctly, then cd to /usr/local/PET/src/build/sage-2.10.2/spkg/build/r-2.6.1.p14 (When you are done debugging, you can type "exit" to leave the subshell.) make[1]: *** [installed/r-2.6.1.p14] Error 1 make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' real 44m44.649s user 41m19.765s sys 2m49.245s build/sage-2.10.2> which gfortran /usr/bin/gfortran build/sage-2.10.2> which g77 g77: Command not found. build/sage-2.10.2> which f77 /opt/ibmcmp/xlf/10.1/bin/f77 build/sage-2.10.2> On Mar 4, 10:20 pm, "Michael.Abshoff" <[EMAIL PROTECTED]> wrote: > Sameer wrote: > > Hi, > > When I try to compile Sage 2.10.2 under ppc64 Linux using gcc, > > I see that some files are > > compiled in 32 bits and some others in 64 bits. Have you noticed this? > > Hi Sameer, > > there is several ways to solve the problem: > > a) Use a gcc that forces 64 bit output per default > b) Wait until 2.10.4 and hope that I have time to merge all the 64 bit > PPC fixes :) > > > > > When I type: > > % make > > I get the following error: > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. -g -O2 -MT > > libiml_la-nullspace.lo -MD -MP -MF .deps/libiml_la-nullspace.Tpo -c > > nullspace.c -o > > libiml_la-nullspace.o >/dev/null 2>&1 > > /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/local/PET/src/build/ > > sage-2.10.2/local/include -I. > > -g -O2 -lm -o libiml.la -rpath /usr/local/PET/src/build/sage-2.10.2/ > > local/lib libiml_la-basisop.lo > > libiml_la-certsolve.lo libiml_la-error.lo libiml_la-latreduce.lo > > libiml_la-memalloc.lo > > libiml_la-mtrans.lo libiml_la-nonsysolve.lo libiml_la-padiclift.lo > > libiml_la-reconsolu.lo > > libiml_la-RNSop.lo libiml_la-nullspace.lo -L/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -lgmp > > ../repl/librepl.la > > gcc -shared .libs/libiml_la-basisop.o .libs/libiml_la- > > certsolve.o .libs/libiml_la-error.o > > .libs/libiml_la-latreduce.o .libs/libiml_la-memalloc.o .libs/libiml_la- > > mtrans.o > > .libs/libiml_la-nonsysolve.o .libs/libiml_la-padiclift.o .libs/ > > libiml_la-reconsolu.o > > .libs/libiml_la-RNSop.o .libs/libiml_la-nullspace.o -Wl,--whole- > > archive ../repl/.libs/librepl.a > > -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/PET/src/build/ > > sage-2.10.2/local/lib -Wl,--rpath > > -Wl,/usr/local/PET/src/build/sage-2.10.2/local/lib -L/usr/local/PET/ > > src/build/sage-2.10.2/local/lib > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so -lm -Wl,- > > soname -Wl,libiml.so.0 -o > > .libs/libiml.so.0.0.0 > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so: could not > > read symbols: File in wrong format > > collect2: ld returned 1 exit status > > make[4]: *** [libiml.la] Error 1 > > make[4]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src/src' > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg/ > > build/iml-1.0.1.p9/src' > > Error building IML > > > real 0m41.850s > > user 0m26.428s > > sys 0m10.164s > > sage: An error occurred while installing iml-1.0.1.p9 > > Please email sage-develhttp://groups.google.com/group/sage-devel > > explaining the problem and send the relevant part of > > of /usr/local/PET/src/build/sage-2.10.2/install.log. Describe your > > computer, operating system, etc. > > If you want to try to fix the problem, yourself *don't* just cd to > > /usr/local/PET/src/build/sage-2.10.2/spkg/build/iml-1.0.1.p9 and type > > 'make'. > > Instead type "/usr/local/PET/src/build/sage-2.10.2/sage -sh" > > in order to set all environment variables correctly, then cd to > > /usr/local/PET/src/build/sage-2.10.2/spkg/build/iml-1.0.1.p9 > > (When you are done debugging, you can type "exit" to leave the > > subshell.) > > make[1]: *** [installed/iml-1.0.1.p9] Error 1 > > make[1]: Leaving directory `/usr/local/PET/src/build/sage-2.10.2/spkg' > > > real 45m41.259s > > user 38m16.037s > > sys 5m3.453s > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so: symbolic > > link to `libgmp.so.3.4.1' > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so.3 > > libgmp.so.3@ libgmp.so.3.4.1* > > build/sage-2.10.2> file /usr/local/PET/src/build/sage-2.10.2/local/lib/ > > libgmp.so.3.4.1 > > /usr/local/PET/src/build/sage-2.10.2/local/lib/libgmp.so.3.4.1: ELF 64- > > bit MSB shared object, cisco > > 7500, version 1 (SYSV), not stripped > > build/sage-2.10.2> file .libs/libiml_la-basisop.o > > .libs/libiml_la-basisop.o: cannot open `.libs/libiml_la-basisop.o' (No > > such file or directory) > > build/sage-2.10.2> file `find . -name libiml_la-basisop.o -print` > > ./spkg/build/iml-1.0.1.p9/src/src/.libs/libiml_la-basisop.o: ELF 32- > > bit MSB relocatable, PowerPC or > > cisco 4500, version 1 (SYSV), not stripped > > ./spkg/build/iml-1.0.1.p9/src/src/libiml_la-basisop.o: ELF 32- > > bit MSB relocatable, PowerPC or > > cisco 4500, version 1 (SYSV), not stripped > > build/sage-2.10.2> which cc > > /usr/bin/cc > > build/sage-2.10.2> cc -c foo.c > > build/sage-2.10.2> file foo.o > > foo.o: ELF 32-bit MSB relocatable, PowerPC or cisco 4500, version 1 > > (SYSV), not stripped > > build/sage-2.10.2> gcc -c foo.c > > build/sage-2.10.2> file foo.o > > foo.o: ELF 32-bit MSB relocatable, PowerPC or cisco 4500, version 1 > > (SYSV), not stripped > > build/sage-2.10.2> rm foo.* > > build/sage-2.10.2> gcc -v > > Using built-in specs. > > Target: powerpc64-suse-linux > > Configured with: ../configure --enable-threads=posix --prefix=/usr -- > > with-local-prefix=/usr/local > > --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib -- > > libexecdir=/usr/lib > > --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable- > > checking=release > > --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable- > > libssp --disable-libgcj--with-slibdir=/lib --with-system-zlib --enable- > > shared --enable-__cxa_atexit > > --enable-libstdcxx-allocator=new --program-suffix= --enable-version- > > specific-runtime-libs > > --without-system-libunwind --with-cpu=default32 --enable-secureplt -- > > with-long-double-128 > > --host=powerpc64-suse-linux > > Thread model: posix > > gcc version 4.1.2 20070115 (prerelease) (SUSE Linux) > > > Should I be looking for a -maix64 or some such flag and remove > > it from the Makefiles? The other > > problem I have is that -lgfortran on my system pointed to /usr/lib/ > > libgfortran.so.1 and this crashed > > the ATLAS compile. After I manually edited the make script, and typed > > make, it tried to rebuild the > > whole thing. I wish there was an option to start off from where the > > error occured. > > Go into spkg/build/$SPKG and look into spkg-install and redo the missing > steps. It usually works if you know what you are doing, but you need to > touch the spkg's basename in spkg/installed after you are done. But I am > sure you will encounter many other problems, especially on startup since > python for example is also likely to be build in 32 bit mode. > > I have played with Python 2.5.2 during the last couple days at Sage Days > 8 and we now can build it on OSX in 64 bit mode, so I know all the > tricks now to make it work on PPC 64, too. > > I am very interested in feedback on the PPC 64 bit port, so ping me > about it in a couple days to hear about progress. > > > Thanks, > > - Sameer > > Cheers, > > Michael > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
