On Sat, Mar 28, 2009 at 9:05 PM, Gonzalo Tornaria <torna...@math.utexas.edu> 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 pulled the new changes into my sage-brandt > branch > 4. applied the rebased 5520 + my tiny patch > 5. sage -br brandt > > But now, "sage -br main" (which is now clean 3.4.1.alpha0) causes the > same issue. > > Gonzalo
Just delete local/lib/sage-flags.txt Also, I've opened a blocker ticket about this (http://trac.sagemath.org/sage_trac/ticket/5628), since everybody who upgrades will run into exactly the same problem. The problem is that the new version of the script that checks the flags doesn't see sse4_1 anymore (nothing in Sage specifically uses that), but it's still in your old sage-flags.txt file. Two possible solutions: (1) delete sage-flags.txt as part of "sage -upgrade" (2) make it so sse4_1 is specifically ignored. I like (1). > > On Sun, Mar 29, 2009 at 12:58 AM, William Stein <wst...@gmail.com> wrote: >> >> On Sat, Mar 28, 2009 at 8:53 PM, Gonzalo Tornaria >> <torna...@math.utexas.edu> 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 clean compile from scratch works fine. >> >> >> >>> Transcript below: >>> >>> torna...@sage:~/sage-3.3.rc0/devel/sage-brandt$ sage >>> ---------------------------------------------------------------------- >>> | Sage Version 3.4.1.alpha0, Release Date: 2009-03-26 | >>> | Type notebook() for the GUI, and license() for information. | >>> ---------------------------------------------------------------------- >>> >>> ********************************************************************** >>> WARNING! This Sage install was built on a machine that supports >>> instructions that are not available on this computer. Sage will >>> likely fail with ILLEGAL INSTRUCTION errors! The following processor >>> flags were on the build machine but are not on this computer: >>> >>> sse4_1 >>> >>> Email http://groups.google.com/group/sage-support for help. >>> To remove this warning and make Sage start, just delete >>> /home/tornaria/sage-3.3.rc0/local/lib/sage-flags.txt >>> ********************************************************************** >>> torna...@sage:~/sage-3.3.rc0/devel/sage-brandt$ grep -c sse4_1 /proc/cpuinfo >>> 24 >>> >>> > >>> >> >> >> >> -- >> William Stein >> Associate Professor of Mathematics >> University of Washington >> http://wstein.org >> >> > >> >> > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
