Maarten Derickx wrote:
Thanks John and Francois, that indeed solved the problem.
I still have to get used a bit to the new workflow and previous time
sage -b just worked, but it's good to know that I have to use make instead.
'./sage -b' never triggered the (re)build of updated (or current) spkgs;
'sage --upgrade' did, but git is no replacement of the latter, as it's
not a package manager.
-leif
Le mercredi 2 avril 2014 11:12:04 UTC+2, François a écrit :
You should have used “make” pynac has to be updated (the source of
your problem)
and sage -b won’t do that.
Francois
On 2/04/2014, at 22:00, Maarten Derickx <m.derick...@gmail.com
<javascript:>> wrote:
> I really like the new git based workflow. It makes it much faster
to update my dev version of sage, however this update failed. Using
OS X 10.9.2 I get:
>
> lll:sage maarten$ sage -b
> scons: `install' is up to date.
> Updating Cython code....
> Finished compiling Cython code (time = 5.498483181 seconds)
> running install
> running build
> running build_py
> running build_ext
> building 'sage.symbolic.function' extension
> building 'sage.symbolic.ring' extension
> building 'sage.symbolic.constants_c' extension
> building 'sage.symbolic.expression' extension
> building 'sage.symbolic.getitem' extension
> building 'sage.symbolic.pynac' extension
> building 'sage.symbolic.substitution_map' extension
> building 'sage.tests.cython' extension
> Executing 8 commands (using 1 thread)
> gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-I/Applications/sage/local/include
-I/Applications/sage/local/include/csage -I/Applications/sage/src
-I/Applications/sage/src/sage/ext -I/Applications/sage/local/include
-I/Applications/sage/local/include/csage -I/Applications/sage/src
-I/Applications/sage/src/sage/ext
-I/Applications/sage/local/include/python2.7 -c
sage/symbolic/function.cpp -o
build/temp.macosx-10.9-x86_64-2.7/sage/symbolic/function.o
-fno-strict-aliasing -w
> In file included from sage/symbolic/function.cpp:350:0:
> sage/symbolic/ginac_wrap.h:12:36: fatal error:
pynac/extern_templates.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-I/Applications/sage/local/include
-I/Applications/sage/local/include/csage -I/Applications/sage/src
-I/Applications/sage/src/sage/ext -I/Applications/sage/local/include
-I/Applications/sage/local/include/csage -I/Applications/sage/src
-I/Applications/sage/src/sage/ext
-I/Applications/sage/local/include/python2.7 -c
sage/symbolic/ring.cpp -o
build/temp.macosx-10.9-x86_64-2.7/sage/symbolic/ring.o
-fno-strict-aliasing -w
> In file included from sage/symbolic/ring.cpp:349:0:
> sage/symbolic/ginac_wrap.h:12:36: fatal error:
pynac/extern_templates.h: No such file or directory
> compilation terminated.
>
>
> Le mercredi 2 avril 2014 02:09:20 UTC+2, Volker Braun a écrit :
> Get it from the "develop" git branch or the source tarball at
http://boxen.math.washington.edu/home/release/sage-6.2.beta6/sage-6.2.beta6.tar.gz
<http://boxen.math.washington.edu/home/release/sage-6.2.beta6/sage-6.2.beta6.tar.gz>
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.