Ask Your Question

# Revision history [back]

### Building ATLAS

I have a little Aspire One "netbook" with 1 Gig of RAM. I used to build sage from source on this machine, but I can't do so anymore. The problem appears to be ATLAS. There is so much output that happens during the ATLAS part of the build that I'm not sure what to post. But in a previous post I think I remember someone saying that ATLAS might need 2 Gig to build. Is this right?

The last time I built on this particular machine was back at Sage 4.3.1. Since then I've also upgraded the OS from Fedora 10 to Fedora 13. I can no longer build 4.3.1 because of the libgcrypt issue with Fedora 13. So I don't know for sure whether my atlas problem is the 1 Gig memory, or some other change with Fedora 13.

So, two specific questions: (1) Does Sage 4.5.2 build on Fedora 13? And, if so, (2) Is there any environment variable I can set to help with the memory issue (if in fact that's what it is)?

-Mike

### Building ATLAS

I have a little Acer Aspire One "netbook" with 1 Gig of RAM. I used to build sage from source on this machine, but I can't do so anymore. The problem appears to be ATLAS. There is so much output that happens during the ATLAS part of the build that I'm not sure what to post. But in post, but I'm open to suggestions on what part of the build output would be pertinent. Here are a previous post I think I remember someone saying that couple of examples of the many errors I get:

/usr/local/sage-4.5.2/spkg/build/atlas-3.8.3.p12/ATLAS-build/bin/xsubstr -o ATL_tMpFiLe -i /usr/local/sage-4.5.2/spkg/build/atlas-3.8.3.p12/ATLAS-build/../src//tune/blas/gemm/CASES/scases.flg \
-s '^gcc' 'gcc -fPIC -m32' -s ' gcc' ' gcc -fPIC -m32'
./xuserflag -i ATL_tMpFiLe -o scases.flg
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
cc1: error: unrecognized command line option "-mips4"

-----------------------------------------------------------------------

ATLAS might need failed to build for the 1-th time, possibly because of a
loaded system, so we will automatically try again up to 4 more times.
Waiting 5 minutes...
ATLAS failed to build for the 2-th time, possibly because of a
loaded system, so we will automatically try again up to 3 more times.
Waiting 12 minutes...
ATLAS failed to build for the 3-th time, possibly because of a
loaded system, so we will automatically try again up to 2 Gig to build. Is this right?more times.
Waiting 8 minutes...
ATLAS failed to build for the 4-th time, possibly because of a
loaded system, so we will automatically try again up to 1 more times.
Waiting 8 minutes...
Too many failures to build ATLAS.  Giving up!


The last time I built on this particular machine was back at Sage 4.3.1. Since then I've also upgraded the OS from Fedora 10 to Fedora 13. I can no longer build 4.3.1 because of the libgcrypt issue with Fedora 13. So I don't know for sure whether my atlas problem is the 1 Gig memory, change to FC-13, the ATLAS build changing, or some other change problem.

Here are the things I've tried so far, without success:

1. Fixing the speed of both CPUs so they won't be throttled back. This didn't help. I'm not running anything else on the machine while I do the build. For comparison, I did the same build on another fairly old 2 processor machine (FC-12). I didn't set the cpu speeds, and I did various other things on that machine at the same time. That build worked with no problem.
2. Doing the same build on another laptop with 1 Gig memory. This worked fine, so I guess memory isn't the problem. The other laptop was an old Think Pad running FC-12.
3. Booting using maxcpus=1 to build with only one CPU (in case there was some weird timing interaction between the 2 CPUs). This didn't help.
4. Using "yum" to install atlas and setting SAGE_ATLAS_LIB to try to get Sage to use the system-wide atlas libraries instead of building them. I've tried setting this up various different ways, but so far have been unable to get it to work. The build always complains that it can't find the files. I imagine I'm doing something wrong here but I can't figure out what.

It appears from the above that the problem must be with either Fedora 13.13, or with something about the Acer Aspire machine. Unfortunately I don't have another FC-13 system set up for comparison.

So, two specific questions: (1) Does Sage 4.5.2 build Any ideas or comments appreciated, particularly:

1. Anybody else using an Aspire One?
2. Anybody have to do anything special to build recently on Fedora 13? And, if so, (2) Is there any environment variable I can set to help with the memory issue (if in fact that's what it is)?

13?

-Mike

 3 retagged FrédéricC 2539 ●3 ●28 ●53

### Building ATLAS

I have a little Acer Aspire One "netbook" with 1 Gig of RAM. I used to build sage from source on this machine, but I can't do so anymore. The problem appears to be ATLAS. There is so much output that happens during the ATLAS part of the build that I'm not sure what to post, but I'm open to suggestions on what part of the build output would be pertinent. Here are a couple of examples of the many errors I get:

/usr/local/sage-4.5.2/spkg/build/atlas-3.8.3.p12/ATLAS-build/bin/xsubstr -o ATL_tMpFiLe -i /usr/local/sage-4.5.2/spkg/build/atlas-3.8.3.p12/ATLAS-build/../src//tune/blas/gemm/CASES/scases.flg \
-s '^gcc' 'gcc -fPIC -m32' -s ' gcc' ' gcc -fPIC -m32'
./xuserflag -i ATL_tMpFiLe -o scases.flg
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
-mcpu=' is deprecated. Use -mtune=' or '-march=' instead.
FlagCheck.c:1: error: bad value (ultrasparc) for -mtune= switch
cc1: error: unrecognized command line option "-mips4"

-----------------------------------------------------------------------

ATLAS failed to build for the 1-th time, possibly because of a
loaded system, so we will automatically try again up to 4 more times.
Waiting 5 minutes...
ATLAS failed to build for the 2-th time, possibly because of a
loaded system, so we will automatically try again up to 3 more times.
Waiting 12 minutes...
ATLAS failed to build for the 3-th time, possibly because of a
loaded system, so we will automatically try again up to 2 more times.
Waiting 8 minutes...
ATLAS failed to build for the 4-th time, possibly because of a
loaded system, so we will automatically try again up to 1 more times.
Waiting 8 minutes...
Too many failures to build ATLAS.  Giving up!


The last time I built on this particular machine was back at Sage 4.3.1. Since then I've also upgraded the OS from Fedora 10 to Fedora 13. I can no longer build 4.3.1 because of the libgcrypt issue with Fedora 13. So I don't know whether my atlas problem is the change to FC-13, the ATLAS build changing, or some other problem.

Here are the things I've tried so far, without success:

1. Fixing the speed of both CPUs so they won't be throttled back. This didn't help. I'm not running anything else on the machine while I do the build. For comparison, I did the same build on another fairly old 2 processor machine (FC-12). I didn't set the cpu speeds, and I did various other things on that machine at the same time. That build worked with no problem.
2. Doing the same build on another laptop with 1 Gig memory. This worked fine, so I guess memory isn't the problem. The other laptop was an old Think Pad running FC-12.
3. Booting using maxcpus=1 to build with only one CPU (in case there was some weird timing interaction between the 2 CPUs). This didn't help.
4. Using "yum" to install atlas and setting SAGE_ATLAS_LIB to try to get Sage to use the system-wide atlas libraries instead of building them. I've tried setting this up various different ways, but so far have been unable to get it to work. The build always complains that it can't find the files. I imagine I'm doing something wrong here but I can't figure out what.

It appears from the above that the problem must be with either Fedora 13, or with something about the Acer Aspire machine. Unfortunately I don't have another FC-13 system set up for comparison.

Any ideas or comments appreciated, particularly:

1. Anybody else using an Aspire One?
2. Anybody have to do anything special to build recently on Fedora 13?

-Mike