Yes, that was exactly what happend!
a second make worked!
and I don't know why!
On Tue, Oct 25, 2011 at 6:21 PM, leif not.rea...@online.de wrote:
On 25 Okt., 21:24, Pablo De Napoli pden...@gmail.com wrote:
I've tried to build Sage 4.7.2 rc0 on a 64 bits Debian GNU/Linux (wheezy/sig)
[Intel core I5 procesor]
The build failed (compiling Atlas)
Here are the eror messages
Thread model: posix
gcc version 4.6.1 (Debian 4.6.1-15)
gcc -V 21 bin/INSTALL_LOG/ERROR.LOG
gcc: error: unrecognized option ‘-V’
gcc: fatal error: no input files
compilation terminated.
make[6]: [error_report] Error 4 (no tiene efecto)
gcc --version 21 bin/INSTALL_LOG/ERROR.LOG
tar cf error_Corei264SSE3.tar Make.inc bin/INSTALL_LOG/*
gzip --best error_Corei264SSE3.tar
mv error_Corei264SSE3.tar.gz error_Corei264SSE3.tgz
make[6]: se sale del directorio
`/home/pablo/sage/sage-4.7.2.rc0/spkg/build/atlas-3.8.4/ATLAS-build'
make[5]: se sale del directorio
`/home/pablo/sage/sage-4.7.2.rc0/spkg/build/atlas-3.8.4/ATLAS-build'
make[4]: se sale del directorio
`/home/pablo/sage/sage-4.7.2.rc0/spkg/build/atlas-3.8.4/ATLAS-build/bin'
Error report error_ARCH.tgz has been created in your top-level ATLAS
directory. Be sure to include this file in any help request.
cat: ../../CONFIG/error.txt: No existe el fichero o el directorio
cat: ../../CONFIG/error.txt: No existe el fichero o el directorio
IN STAGE 1 INSTALL: SYSTEM PROBE/AUX COMPILE
make[3]: *** [build] Error 255
make[3]: se sale del directorio
`/home/pablo/sage/sage-4.7.2.rc0/spkg/build/atlas-3.8.4/ATLAS-build'
make[2]: *** [build] Error 2
make[2]: se sale del directorio
`/home/pablo/sage/sage-4.7.2.rc0/spkg/build/atlas-3.8.4/ATLAS-build'
My version of gcc is:
$ gcc --version
gcc (Debian 4.6.1-15) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
gcc -V gives
gcc -V
gcc: error: unrecognized option ‘-V’
gcc: fatal error: no input files
compilation terminated.
Well, the error occurred earlier. ATLAS then simply tries to get the
compiler's version for the error report, which finally succeeds.
As the log says, the relevant messages / ATLAS build logs are in
error_Corei264SSE3.tgz.
Sometimes just doing a second build attempt (by simply typing 'make')
succeeds. Assuming you've disabled CPU throttling, aka power saving
mode. Also the system load shouldn't be too high when building ATLAS.
-leif
--
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
