I had the same problem with git-1.8.4.4. This is running on CentOS (which
is a ridiculous pain for someone who doesn't really know what they're
doing...).
I tried running the command Volker suggested: `yum install
perl-ExtUtils-MakeMaker`
I get the following error:
Loaded plugins: security
Re
Did Apple break isatty or whats going on?
On Friday, December 20, 2013 10:42:56 AM UTC, Marco Streng wrote:
>
> Built succesfully on OSX 10.9.1 (well, on 1 of the 2 machines). But sage
> -t -a gives:
>
> sage -t src/sage/interfaces/sage0.py # 4 doctests failed
> sage -t src/sage/structure/sage_o
Built succesfully on OSX 10.9.1 (well, on 1 of the 2 machines). But sage -t
-a gives:
sage -t src/sage/interfaces/sage0.py # 4 doctests failed
sage -t src/sage/structure/sage_object.pyx # 3 doctests failed
sage -t src/sage/doctest/forker.py # 2 doctests failed
sage -t src/sage/misc/ascii_art.py
2013/12/19 Jeroen Demeyer
> On 2013-12-19 15:08, Marco Streng wrote:
>
>> New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
>> after downloading and extracting the tarball and typing "make", I get
>> the following problem (both sage 5.13 and sage 6.0).
>>
>> sed: /usr/includ
On 2013-12-19 15:08, Marco Streng wrote:
New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
after downloading and extracting the tarball and typing "make", I get
the following problem (both sage 5.13 and sage 6.0).
sed: /usr/include/sys/cdefs.h: No such file or directory
Thi
New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
after downloading and extracting the tarball and typing "make", I get the
following problem (both sage 5.13 and sage 6.0).
sed: /usr/include/sys/cdefs.h: No such file or directory
Marco
-
Found package gcc-4.7.3.p1
--
All tests passed!
--
Total time for all tests: 1036.7 seconds
cpu time: 6876.2 seconds
cumulative wall time: 7838.4 seconds
On Thu, Dec 19, 2013 at
[jaap@vrede sage-6.0]$ gcc --version
gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-7)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[jaap@vrede sage-
On Wednesday, December 18, 2013 3:05:13 PM UTC-8, Volker Braun wrote:
>
> For the git problem you need to "yum install perl-ExtUtils-MakeMaker".
>
> For the atlas problem I need the whole log. One alternative is to install
> the system atlas ("yum install atlas-devel") and build with
> SAGE_ATL
My goodness! How should I have known this!
Jaap
On Thu, Dec 19, 2013 at 12:05 AM, Volker Braun wrote:
> For the git problem you need to "yum install perl-ExtUtils-MakeMaker".
>
> For the atlas problem I need the whole log. One alternative is to install
> the system atlas ("yum install atlas-dev
For the git problem you need to "yum install perl-ExtUtils-MakeMaker".
For the atlas problem I need the whole log. One alternative is to install
the system atlas ("yum install atlas-devel") and build with
SAGE_ATLAS_LIB=/usr/lib64/atlas
On Wednesday, December 18, 2013 10:17:36 PM UTC, jaap wr
Yay! Congrats and thank you.
On Wed, Dec 18, 2013 at 3:00 AM, Volker Braun wrote:
> Sage 6.0
>
> A.k.a. "Today is a good day to die", the credo of release engineering...
>
> This is the first official release for Sage 6, which from now on will use
> git and a single unified repository.
>
> Source
Thanks Harald.
Thread model: posix
gcc version 4.7.3 (GCC)
/home/jaap/downloads/sage-6.0/local/bin/gcc -V 2>&1 >>
bin/INSTALL_LOG/ERROR.LOG
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
make[7]: [error_report] Error 1 (ignored)
/home/ja
On Wed, Dec 18, 2013 at 10:49 PM, Jaap Spies wrote:
> Please, tell me more exact what you want to see. I'm rusty in building Sage!
The error message mentions log files for both packages, i.e.
log file: /home/jaap/downloads/sage-6.0/
logs/pkgs/atlas-3.10.1.p7.log
and
log file: /home/jaap/downloa
Please, tell me more exact what you want to see. I'm rusty in building Sage!
Jaap
On Wed, Dec 18, 2013 at 10:38 PM, Volker Braun wrote:
> I updated to Fedora 20 this morning and Sage built for me. Can you post
> the logs?
>
>
>
> On Wednesday, December 18, 2013 9:22:14 PM UTC, jaap wrote:
>
>
I updated to Fedora 20 this morning and Sage built for me. Can you post the
logs?
On Wednesday, December 18, 2013 9:22:14 PM UTC, jaap wrote:
>
> Sorry to disturb your day. Please don't die.
>
> I upgraded to Fedora 20, but building sage-6.0 resulted in:
> Error building Sage.
>
> The following
Sorry to disturb your day. Please don't die.
I upgraded to Fedora 20, but building sage-6.0 resulted in:
Error building Sage.
The following package(s) may have failed to build:
package: atlas-3.10.1.p7
log file: /home/jaap/downloads/sage-6.0/logs/pkgs/atlas-3.10.1.p7.log
build directory:
/home/j
Yo !!
> A.k.a. "Today is a good day to die", the credo of release engineering...
Gosh ! This release is gloomier than usual :-P
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop re
Sage 6.0
A.k.a. "Today is a good day to die", the credo of release engineering...
This is the first official release for Sage 6, which from now on will use
git and a single unified repository.
Source tarball:
http://boxen.math.washington.edu/home/vbraun/src/sage-6.0.tar.gz
Binary tarballs (i
19 matches
Mail list logo
