I tried to build sage-5.3 on the new desktop my department has just
supplied me with (on which I do not have root access), and atlas
failed to configure.
uname -a
Linux host-56-160 3.0.38-0.5-default #1 SMP Fri Aug 3 09:02:17 UTC
2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux
On Thursday, October 4, 2012 11:51:52 AM UTC+1, John Cremona wrote:
> I tried to build sage-5.3 on the new desktop my department has just > supplied me with (on which I do not have root access), and atlas > failed to configure.
> uname -a > Linux host-56-160 3.0.38-0.5-default #1 SMP Fri Aug 3 09:02:17 UTC > 2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux
> On Thursday, October 4, 2012 11:51:52 AM UTC+1, John Cremona wrote:
>> I tried to build sage-5.3 on the new desktop my department has just
>> supplied me with (on which I do not have root access), and atlas
>> failed to configure.
>> uname -a
>> Linux host-56-160 3.0.38-0.5-default #1 SMP Fri Aug 3 09:02:17 UTC
>> 2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux
>> First attempt: automatic tuning.
>> Running configure with arch = None and isa extensions None
>> Running ../src/configure --prefix=/local/masgaj/sage-5.3/local
>> --with-netlib-lapack=/local/masgaj/sage-5.3/local/lib/liblapack.a
>> --cc="gcc" -Si cputhrchk 0 -Fa alg -fPIC -C if sage_fortran -C xc
>> "gcc" -C ic "gcc" -C dm "gcc" -C sm "gcc" -C dk "gcc" -C sk "gcc" -b
>> 64 -O 1
>> Traceback (most recent call last):
>> File "./spkg-install", line 442, in <module>
>> rc = build()
>> File "./spkg-install", line 431, in build
>> assert rc==0, 'Configure failed!'
>> AssertionError: Configure failed!
>> John
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to
> sage-devel+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
1. #10508 had various dependencies now merged in 5.4 so I switched to
building 5.4.rc0 instead of 5.3. (This is a machine I will not be
doing development on so normally only build real releases).
2. I downloaded the new atlas and cvxopt spkgs from that ticket to
SAGE_ROOT/spkg/standard
3. Before starting to build, I see that tehre are two patches to be
applied. I normally do that using hg, but this machine has an old
version (1.0.2) and I cannot do hg import without getting the error
abort: requirement 'fncache' not supported!
So I applied the first patch (needed for building) using "patch"
instead of "hg" and have left the other two until later as they only
involve documentation and doctests.
> On Thursday, October 4, 2012 11:51:52 AM UTC+1, John Cremona wrote:
>> I tried to build sage-5.3 on the new desktop my department has just
>> supplied me with (on which I do not have root access), and atlas
>> failed to configure.
>> uname -a
>> Linux host-56-160 3.0.38-0.5-default #1 SMP Fri Aug 3 09:02:17 UTC
>> 2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux
>> First attempt: automatic tuning.
>> Running configure with arch = None and isa extensions None
>> Running ../src/configure --prefix=/local/masgaj/sage-5.3/local
>> --with-netlib-lapack=/local/masgaj/sage-5.3/local/lib/liblapack.a
>> --cc="gcc" -Si cputhrchk 0 -Fa alg -fPIC -C if sage_fortran -C xc
>> "gcc" -C ic "gcc" -C dm "gcc" -C sm "gcc" -C dk "gcc" -C sk "gcc" -b
>> 64 -O 1
>> Traceback (most recent call last):
>> File "./spkg-install", line 442, in <module>
>> rc = build()
>> File "./spkg-install", line 431, in build
>> assert rc==0, 'Configure failed!'
>> AssertionError: Configure failed!
>> John
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to
> sage-devel+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> 2. I downloaded the new atlas and cvxopt spkgs from that ticket to
> SAGE_ROOT/spkg/standard
Good.
> 3. Before starting to build, I see that tehre are two patches to be
> applied.
Not sure where you get the number "two" from, I assume you meant either
"one" or "three", depending on what you count.
> So I applied the first patch (needed for building) using "patch"
> instead of "hg" and have left the other two until later as they only
> involve documentation and doctests.
I don't know what will happen when the SAGE_ROOT spkg is installed. In
the worst case, it would fail because of uncommitted changes. Let's
hope not, and then this would indeed be the correct way.
On 4 October 2012 12:59, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2012-10-04 13:41, John Cremona wrote:
>> 2. I downloaded the new atlas and cvxopt spkgs from that ticket to
>> SAGE_ROOT/spkg/standard
> Good.
>> 3. Before starting to build, I see that tehre are two patches to be
>> applied.
> Not sure where you get the number "two" from, I assume you meant either
> "one" or "three", depending on what you count.
I had miscounted indeed!
>> So I applied the first patch (needed for building) using "patch"
>> instead of "hg" and have left the other two until later as they only
>> involve documentation and doctests.
> I don't know what will happen when the SAGE_ROOT spkg is installed. In
> the worst case, it would fail because of uncommitted changes. Let's
> hope not, and then this would indeed be the correct way.
We'll see. It has not failed yet (currently building gfan)...
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to sage-devel+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> On 4 October 2012 12:59, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
>> On 2012-10-04 13:41, John Cremona wrote:
>>> 2. I downloaded the new atlas and cvxopt spkgs from that ticket to
>>> SAGE_ROOT/spkg/standard
>> Good.
>>> 3. Before starting to build, I see that tehre are two patches to be
>>> applied.
>> Not sure where you get the number "two" from, I assume you meant either
>> "one" or "three", depending on what you count.
> I had miscounted indeed!
>>> So I applied the first patch (needed for building) using "patch"
>>> instead of "hg" and have left the other two until later as they only
>>> involve documentation and doctests.
>> I don't know what will happen when the SAGE_ROOT spkg is installed. In
>> the worst case, it would fail because of uncommitted changes. Let's
>> hope not, and then this would indeed be the correct way.
> We'll see. It has not failed yet (currently building gfan)...
> John
>> --
>> You received this message because you are subscribed to the Google Groups "sage-devel" group.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> To unsubscribe from this group, send email to sage-devel+unsubscribe@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> ideas? It's not serious, I am doing a full doctest anyway and will > see if anything appears not addressed by that (unapplied) patch.
> John
> On 4 October 2012 13:20, John Cremona <john.c...@gmail.com <javascript:>> > wrote: > > On 4 October 2012 12:59, Jeroen Demeyer <jdem...@cage.ugent.be<javascript:>> > wrote: > >> On 2012-10-04 13:41, John Cremona wrote: > >>> 2. I downloaded the new atlas and cvxopt spkgs from that ticket to > >>> SAGE_ROOT/spkg/standard > >> Good.
> >>> 3. Before starting to build, I see that tehre are two patches to be > >>> applied. > >> Not sure where you get the number "two" from, I assume you meant either > >> "one" or "three", depending on what you count.
> > I had miscounted indeed!
> >>> So I applied the first patch (needed for building) using "patch" > >>> instead of "hg" and have left the other two until later as they only > >>> involve documentation and doctests. > >> I don't know what will happen when the SAGE_ROOT spkg is installed. In > >> the worst case, it would fail because of uncommitted changes. Let's > >> hope not, and then this would indeed be the correct way.
> > We'll see. It has not failed yet (currently building gfan)...
> > John
> >> -- > >> You received this message because you are subscribed to the Google > Groups "sage-devel" group. > >> To post to this group, send email to sage-...@googlegroups.com<javascript:>.
> Note the /raw-attachment/ instead of /attachment/ in the url.
Sorry, that was stupid of me. ANyway, all the doctests except the one
which that patch fixed did pass, and I now have a working 5.4.rc0 on
the new machine, built with the new atlas spkg, total build time 90m.