Sage on Maemo 5
mmarco
run sage in it. I imagine that porting such a big collection of
software that deppends on such a variety of languages and libraries
would be extremelly hard, but anyways i thought it would be worth
asking to experts: do you think it would be possible?
From what i have read, the recompilation of pure C code shouldn't be
problematic, i have read that some people got to compile maxima in
older versions of maemo, and it seems to be also a python version.
So, what do you think? would it be possible?
Harald Schilly
is possible ;)
h
Georg S. Weber
Actually, I think it is rather easy to port Sage to the N900.
Due to the "batteries included" concept Sage uses, Sage is very
porting-friendly.
Maybe end of March, I'll get a N900 for myself. If so, I will
certainly play around with it. One issue is, that (at least fot the
time being) I work on Mac(s) exclusively, and the Maemo SDK needs
Linux as a host, so I'd need something like VirtualBox to work well
with the Maemo SDK's "scratchbox". Also, the Cortex A8 CPU might be
"new" to e.g. MPIR or ATLAS, but given that it is also an ARM-
derivative just like the CPU of the G1, I don't expect any trouble not
some tiny fixes away.
Cheers,
Georg
mmarco
error.
What i did is the following:
1)Run the maemo sdk virtual image on virtualbox (i didn't want to
install the sdk manually, so i opted for the easy option)
2)Unpack the sage source in a directory
3) Log in to scratchbox (it is the cross-compiling environment used
for arm/maemo).
4) cd to the directory where i unpacked sage code
5) make
The compilation went on fine for a while. But after around an hour, i
got the following output:
make[2]: Entering directory `/home/maemo/workspace/sage-4.3.1/spkg/
build/cliquer-1.2.p2/src'
gcc -O2 -g -Wall -fomit-frame-pointer -funroll-loops -c -fPIC -
DENABLE_LONG_OPTIONS -o cl.o -c cl.c
gcc -O2 -g -Wall -fomit-frame-pointer -funroll-loops -c -fPIC -I/
home/maemo/workspace/sage-4.3.1/local/include -c -o cliquer.o
cliquer.c
gcc -O2 -g -Wall -fomit-frame-pointer -funroll-loops -c -fPIC -I/
home/maemo/workspace/sage-4.3.1/local/include -c -o graph.o graph.c
gcc -O2 -g -Wall -fomit-frame-pointer -funroll-loops -c -fPIC -I/
home/maemo/workspace/sage-4.3.1/local/include -c -o reorder.o
reorder.c
gcc -L/home/maemo/workspace/sage-4.3.1/local/lib -shared -Wl,-
soname,libcliquer.so -o libcliquer.so cl.o cliquer.o graph.o reorder.o
make[2]: Leaving directory `/home/maemo/workspace/sage-4.3.1/spkg/
build/cliquer-1.2.p2/src'
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/scratchbox/tools/bin/mkdir", line 3, in ?
import sys, os, sb.config
File "/home/maemo/workspace/sage-4.3.1/local/lib/python/os.py", line
120
from os.path import (curdir, pardir, sep, pathsep, defpath,
extsep, altsep,
^
SyntaxError: invalid syntax
real 0m1.496s
user 0m0.248s
sys 0m0.656s
sage: An error occurred while installing cliquer-1.2.p2
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/maemo/workspace/sage-4.3.1/install.log. Describe your
computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/maemo/workspace/sage-4.3.1/spkg/build/cliquer-1.2.p2 and type
'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/home/maemo/workspace/sage-4.3.1/spkg/build/cliquer-1.2.p2' && '/
home/maemo/workspace/sage-4.3.1/sage' -sh)
When you are done debugging, you can type "exit" to leave the
subshell.
make[1]: *** [installed/cliquer-1.2.p2] Error 1
make[1]: Leaving directory `/home/maemo/workspace/sage-4.3.1/spkg'
real 0m3.148s
user 0m0.412s
sys 0m1.340s
Error building Sage.
Any clue about how to solve this?
William Stein
What happens if you type this:
cd /home/maemo/workspace/sage-4.3.1
./sage -python
import sys, os
-- William
mmarco
> What happens if you type this:
>
> cd /home/maemo/workspace/sage-4.3.1
> ./sage -python
> import sys, os
>
> -- William
Nothing noticeable:
[sbox-FREMANTLE_ARMEL: ~/workspace/sage-4.3.1] > ./sage -python
Python 2.6.4 (r264:75706, Jan 23 2010, 12:32:46)
[GCC 4.2.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys, os
>>>
Georg S. Weber
this is nothing but a wild guess (deduced from hits after some
searching "scratchbox python" in the web, as for why calling python in
the scratchbox is problematic, see e.g.:
http://lists.scratchbox.org/pipermail/scratchbox-users/2005-May/000250.html
or http://osdir.com/ml/compilers.scratchbox.user/2006-06/msg00033.html).
But maybe worth a try:
export SBOX_REDIRECT_IGNORE=/home/maemo/workspace/sage-4.3.1/local/
python
The path name is also guessed, from your log snippet above ...
Cheers,
Georg
mmarco
> export SBOX_REDIRECT_IGNORE=/home/maemo/workspace/sage-4.3.1/local/
> python
>
Tried that. Didn't work :(
Any more clues?
Georg S. Weber
Nope, sorry.
I think that somehow (the call to) Python is screwed up in this
setting --- but still, it could be something else. However, "from the
distance", I feel I can't give valuable advice. Unfortunately, it will
be weeks (rather months) before I can have a closer look (installing
this) myself.
Cheers,
Georg
mmarco
Ok, i have gone with a new attepmt, compiling sage in the phone
itself.
What i did is to install the easy-deb-chroot package (it basically
mounts a disk image with a debian-arm system, and chroots into it).
Then i installed in that echroot environment the needed tools (build-
essential, m4 and gfortran),and tried to compile sage.
As before, the compilation process went on for several hours, but at
some point, it crashed with the following output:
Finished extraction
****************************************************
Host system
uname -a:
Linux Nokia-N900-42-11 2.6.28-omap1 #1 PREEMPT Thu Dec 17 09:40:52 EET
2009 armv7l GNU/Linux
****************************************************
****************************************************
CC Version
gcc -v
Using built-in specs.
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='Debian
4.3.4-6' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --
enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-
shared --enable-multiarch --enable-linker-build-id --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --enable-
threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --
enable-objc-gc --enable-mpfr --disable-sjlj-exceptions --enable-
checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --
target=arm-linux-gnueabi
Thread model: posix
gcc version 4.3.4 (Debian 4.3.4-6)
****************************************************
Platform detected to be 32 bits
system_atlas.py:6: DeprecationWarning: os.popen2 is deprecated. Use
the subprocess module.
fortran = os.popen2(os.environ['SAGE_LOCAL']+'/bin/'+'which_fortran')
[1].read()
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_PAPER = "es_ES",
LC_ADDRESS = "es_ES",
LC_MONETARY = "es_ES",
LC_NUMERIC = "es_ES",
LC_TELEPHONE = "es_ES",
LC_MESSAGES = "es_ES",
LC_IDENTIFICATION = "es_ES",
LC_MEASUREMENT = "es_ES",
LC_TIME = "es_ES",
LC_NAME = "es_ES",
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
/sage-4.3.1/spkg/build/atlas-3.8.3.p10
Deal with PPC4 7447 model and Itanium 2
Updating archinfo_x86.c
Updating probe_comp.c
Updating Make.top
make[2]: Entering directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
gcc -I/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//
CONFIG/include -g -w -c /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-
build/../src//CONFIG/src/atlconf_misc.c
gcc -I/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//
CONFIG/include -g -w -o xconfig /sage-4.3.1/spkg/build/
atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/config.c
atlconf_misc.o
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
make[2]: Leaving directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
./xconfig -d s /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../
src/ -d b /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build -Ss
flapack /sage-4.3.1/local/lib/liblapack.a -Si cputhrchk 0 -Fa alg -
fPIC -t 0 -C if /sage-4.3.1/local/bin/sage_fortran -b 32
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
make[3]: *** [atlas_run] Error 1
make[2]: *** [IRun_asm] Error 2
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S: Assembler messages:
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:30: Error: bad instruction `subl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:31: Error: bad instruction `movl %ebx,(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:32: Error: bad instruction `movl %edi,4(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:36: Error: bad instruction `movl 16(%esp),%eax'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:37: Error: bad instruction `cpuid'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:41: Error: bad instruction `movl 12(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:42: Error: bad instruction `movl %eax,(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:43: Error: bad instruction `movl %ebx,4(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:44: Error: bad instruction `movl %ecx,8(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:45: Error: bad instruction `movl %edx,12(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:49: Error: bad instruction `movl (%esp),%ebx'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:50: Error: bad instruction `movl 4(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:51: Error: bad instruction `addl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:52: Error: bad instruction `ret'
make[4]: *** [xarchinfo_x86] Error 1
atlconf_misc_BE.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S: Assembler messages:
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:30: Error: bad instruction `subl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:31: Error: bad instruction `movl %ebx,(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:32: Error: bad instruction `movl %edi,4(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:36: Error: bad instruction `movl 16(%esp),%eax'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:37: Error: bad instruction `cpuid'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:41: Error: bad instruction `movl 12(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:42: Error: bad instruction `movl %eax,(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:43: Error: bad instruction `movl %ebx,4(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:44: Error: bad instruction `movl %ecx,8(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:45: Error: bad instruction `movl %edx,12(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:49: Error: bad instruction `movl (%esp),%ebx'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:50: Error: bad instruction `movl 4(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:51: Error: bad instruction `addl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:52: Error: bad instruction `ret'
make[4]: *** [xarchinfo_x86] Error 1
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S: Assembler messages:
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:30: Error: bad instruction `subl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:31: Error: bad instruction `movl %ebx,(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:32: Error: bad instruction `movl %edi,4(%esp)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:36: Error: bad instruction `movl 16(%esp),%eax'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:37: Error: bad instruction `cpuid'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:41: Error: bad instruction `movl 12(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:42: Error: bad instruction `movl %eax,(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:43: Error: bad instruction `movl %ebx,4(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:44: Error: bad instruction `movl %ecx,8(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:45: Error: bad instruction `movl %edx,12(%edi)'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:49: Error: bad instruction `movl (%esp),%ebx'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:50: Error: bad instruction `movl 4(%esp),%edi'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:51: Error: bad instruction `addl $8,%esp'
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
backend/cpuid.S:52: Error: bad instruction `ret'
make[4]: *** [xarchinfo_x86] Error 1
It appears you have cpu throttling enabled, which makes timings
unreliable and an ATLAS install nonsensical. Aborting.
See ATLAS/INSTALL.txt for further information
Ignoring CPU throttling by user override!
make[2]: Entering directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
gcc -I/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//
CONFIG/include -g -w -c /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-
build/../src//CONFIG/src/probe_comp.c
gcc -I/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//
CONFIG/include -g -w -o xprobe_comp probe_comp.o atlconf_misc.o
atlconf_misc.o: In function `CmndResults':
/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//CONFIG/src/
atlconf_misc.c:306: warning: the use of `tmpnam' is dangerous, better
use `mkstemp'
rm -f config1.out
make atlas_run atldir=/sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-
build exe=xprobe_comp args="-v 0 -o atlconf.txt -O 1 -A 0 -Si nof77 0
-Fa ic '-fPIC' -Fa sm '-fPIC' -Fa dm '-fPIC' -Fa sk '-fPIC' -Fa dk '-
fPIC' -Fa xc '-fPIC' -C if '/sage-4.3.1/local/bin/sage_fortran' -Fa if
'-fPIC' -b 32" \
redir=config1.out
make[3]: Entering directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
cd /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build ; ./xprobe_comp -
v 0 -o atlconf.txt -O 1 -A 0 -Si nof77 0 -Fa ic '-fPIC' -Fa sm '-
fPIC' -Fa dm '-fPIC' -Fa sk '-fPIC' -Fa dk '-fPIC' -Fa xc '-fPIC' -C
if '/sage-4.3.1/local/bin/sage_fortran' -Fa if '-fPIC' -b 32 >
config1.out
cc1: error: unrecognized command line option "-m32"
make[4]: *** [IRunCComp] Error 1
Unable to find usable compiler for ICC; abortingMake sure compilers
are in your path, and specify good compilers to configure
(see INSTALL.txt or 'configure --help' for details)make[3]: ***
[atlas_run] Error 1
make[3]: Leaving directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
make[2]: *** [IRun_comp] Error 2
make[2]: Leaving directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
xconfig: /sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src//
CONFIG/src/config.c:125: ProbeComp: Assertion `!system(ln)' failed.
OS configured as Linux (1)
Bad ASM value=0, ierr=1, ln2=''
Assembly configured as (0)
Bad VECFLAG value=0, ierr=0, ln2='VECFLAG=0
'
Vector ISA Extension configured as (0,0)
Bad MACHTYPE value=0, ierr=0, ln2='MACHTYPE=0
'
Architecture configured as UNKNOWN (0)
Bad CPU MHZ value=0, ierr=0, ln2='CPU MHZ=0
'
Clock rate configured as 0Mhz
CPU Throttling apparently enabled!
/bin/sh: line 1: 5640 Aborted ./xconfig -d s /
sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build/../src/ -d b /
sage-4.3.1/spkg/build/atlas-3.8.3.p10/ATLAS-build -Ss flapack /
sage-4.3.1/local/lib/liblapack.a -Si cputhrchk 0 -Fa alg -fPIC -t 0 -C
if /sage-4.3.1/local/bin/sage_fortran -b 32
xconfig exited with 134
make[2]: Entering directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
make -f Make.top build
make[3]: Entering directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
make[3]: Make.top: No such file or directory
make[3]: *** No rule to make target `Make.top'. Stop.
make[3]: Leaving directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/sage-4.3.1/spkg/build/atlas-3.8.3.p10/
ATLAS-build'
Failed to build ATLAS.
Failed to build ATLAS.
real 0m46.501s
user 0m16.258s
sys 0m6.867s
sage: An error occurred while installing atlas-3.8.3.p10
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /sage-4.3.1/install.log. Describe your computer, operating system,
etc.
If you want to try to fix the problem yourself, *don't* just cd to
/sage-4.3.1/spkg/build/atlas-3.8.3.p10 and type 'make check' or
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/sage-4.3.1/spkg/build/atlas-3.8.3.p10' && '/sage-4.3.1/sage' -
sh)
When you are done debugging, you can type "exit" to leave the
subshell.
make[1]: *** [installed/atlas-3.8.3.p10] Error 1
make[1]: Leaving directory `/sage-4.3.1/spkg'
real 1m25.222s
user 0m35.258s
sys 0m9.250s
Error building Sage.
Georg S. Weber
building the atlas spkg currently fails (whoa! spectacularly so!) on
ARM. This was reported also in another thread two weeks ago:
But I don't know what the current status is.
Cheers,
Georg
mmarco
fails. Is it possible to compile sage without atlas?. I would rather
have a sage installation with some features missing, than having no
sage at all.
Cheers,
Miguel
Dr. David Kirkby
I don't know if that might cause any problems later. Some packages may rely on
ATLAS, but I don't know.
Could you post the error message from ATLAS. There have been a lot of problems
wtih ATLAS on Sage - specifically to those on Solaris, but workarounds have been
found to all of them, even though there is no official new ATLAS release which
addresses these points.
It may be possible to fix the ATLAS issues quite easily.
Dave
mmarco
> Could you post the error message from ATLAS. There have been a lot of problems
> wtih ATLAS on Sage - specifically to those on Solaris, but workarounds have been
> found to all of them, even though there is no official new ATLAS release which
> addresses these points.
>
> It may be possible to fix the ATLAS issues quite easily.
>
> Dave
I wrote the error message in this thread a few days ago:
http://groups.google.com/group/sage-devel/msg/6a0350566bfd83fc?
If someone comes with some ideas for workarounds, i can try them.