(1) Version 2.7.1 installed and compiled fine on a suse 10.2 amd64 machine.
SAGE build/upgrade complete!
[EMAIL PROTECTED]:~/sagefiles/sage-2.7.1.alpha3> ./sage
----------------------------------------------------------------------
| SAGE Version 2.7.1.alpha3, Release Date: 2007-07-22                |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------

sage: 2+3.0
5.00000000000000
sage:


(2) Version 2.7 did not install without errors (on the same machine):


****************************************************
Host system
uname -a:
Linux wooster 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
x86_64 x86_64 x86_64 GNU/Linux
****************************************************
****************************************************
GCC Version
gcc -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
ndir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enachecking=release --with-gxx-include-dir=/usr/include/c++/4.1.2
--enable-ssp --disable-libssp --disable-libgcj --with-slibdirb64
--with-system-zlib --enable-shared --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --program-suffix=-4.1
--enablesion-specific-runtime-libs --without-system-libunwind
--with-cpu=generic --host=x86_64-suse-linux
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
****************************************************
which: no gfortran in
(/home/wdj/sagefiles/sage-2.7:/home/wdj/sagefiles/sage-2.7/local/bin:/home/wdj/sagefiles/sage-2.7:/homj/sagefiles/sage-2.7/local/bin:/home/wdj/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3:/usr/lib/mit/bin:/usr/lib/mit/sbin)
Using SAGE Server http://www.sagemath.org//packages




**********************************************************************



Error installing Fortran: On your system, you must install the
gfortran VERSION 4.x compiler *manually* before in




**********************************************************************



real    0m0.069s
user    0m0.052s
sys     0m0.016s
sage: An error occured while installing gfortran-20070719
Please email William Stein <[EMAIL PROTECTED]> explaining the
problem and send him the relevant part of
of /home/wdj/sagefiles/sage-2.7/install.log.  Don't send the whole thing.
If you want to try to fix the problem, yourself *don't* just cd to
/home/wdj/sagefiles/sage-2.7/spkg/build/gfortran-20070719 and type 'make'.
Instead (using bash) type "source local/bin/sage-env" from the directory
/home/wdj/sagefiles/sage-2.7
in order to set all environment variables correctly, then cd to
/home/wdj/sagefiles/sage-2.7/spkg/build/gfortran-20070719
make[1]: *** [installed/gfortran-20070719] Error 1
make[1]: Leaving directory `/mnt/hd200/sagefiles/sage-2.7/spkg'

real    37m30.401s
user    22m19.904s
sys     6m54.354s
[EMAIL PROTECTED]:~/sagefiles/sage-2.7>

(3) Version 2.7 installed fine on both an intel macbook (10.4 OS X)
and on a 32bit fisty fawn ubuntu (*finally* back from the repair shop).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On 7/22/07, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> This weekend Josh Kantor and I redid the new SAGE build system so that
>   (1) it uses g95 instead of gfortran, and
>   (2) it includes the g95 binaries (instead of downloading them during
> the build).
>
> It would be incredibly useful to Josh Kantor and I if a few of you
> could download the
> tarball here:
>
>        http://sage.math.washington.edu/home/was/sage2.7.1/
>
> extract it, type "make", and let me know what happens.  I.e., does it
> build or not?
> I'm interested mainly in building on 64-bit linux installs, then
> 32-bit linux installs,
> then os x (powerpc).   The output of "make test", might also be
> interested, though I know
> that 2 or 3 tests will fail.   Another good test that scipy built
> correctly is that
>
>     sage: import scipy.optimize
>
> doesn't bomb out.  (I know it bombs out on powerpc os x, and haven't figured 
> out
> why -- it should work on everything else).
>
> Many thanks for any build feedback.  And of course any comments about
> using g95, our whole build approach, etc., would be appreciated (the comments
> last week were very helpful -- there's no weird g2c ar stuff going on
> any more).
>
>  -- William
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washington
> http://www.williamstein.org
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to