On Sat, Mar 28, 2009 at 9:13 PM, mabshoff wrote:
>
>
>
> On Mar 28, 9:05 pm, Gonzalo Tornaria wrote:
>> I did an upgrade from 3.4 as follows:
>>
>> 1. sage -br main ---> switch to main, which is CLEAN
>> 2. sage
>> -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sa..
On Mar 28, 9:05 pm, Gonzalo Tornaria wrote:
> I did an upgrade from 3.4 as follows:
>
> 1. sage -br main ---> switch to main, which is CLEAN
> 2. sage
> -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sa...
> 3. once that was finished, I pulled the new changes into
On Sat, Mar 28, 2009 at 9:05 PM, Gonzalo Tornaria
wrote:
>
> I did an upgrade from 3.4 as follows:
>
> 1. sage -br main ---> switch to main, which is CLEAN
> 2. sage -upgrade
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sage-3.4.1.alpha0
> 3. once that was finished, I pul
I did an upgrade from 3.4 as follows:
1. sage -br main ---> switch to main, which is CLEAN
2. sage -upgrade
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sage-3.4.1.alpha0
3. once that was finished, I pulled the new changes into my sage-brandt branch
4. applied the rebased
On Sat, Mar 28, 2009 at 8:53 PM, Gonzalo Tornaria
wrote:
>
> I've just finished compilation of 3.4.1.alpha0 + small patches in
> sage.math, but it refuses to run based on "missing sse4_1 flag".
> However, sage.math seems to still have 24 cores all of them with
> sse4_1...
Did you upgrade? A c
On Mar 28, 8:53 pm, Gonzalo Tornaria wrote:
> I've just finished compilation of 3.4.1.alpha0 + small patches in
> sage.math, but it refuses to run based on "missing sse4_1 flag".
> However, sage.math seems to still have 24 cores all of them with
> sse4_1...
Did you upgrade another build? I can
