This sounds like a great idea! I'll get started on one that hopefully
doesn't overlap with anyone else's's area of expertise.
I'm very keen to contribute to the project in any way I can...
Vince
On 17 December 2013 21:13, Jeroen Demeyer wrote:
> On 2013-12-17 21:05, John Cremona wrote:
>
>> At
I put that into gdb; the problem seems to originate in emacs.
Summary:
1) Yes, I killed the make procress several time, sorry I forgot that this
would extend the log file, and I stupidly copied the whole thing.
2) No CPU activity.
3) It seems that the following command is to be blamed:
emacs -q -
On Wed, Dec 18, 2013 at 9:35 AM, Vincent Knight wrote:
> This sounds like a great idea! I'll get started on one that hopefully
> doesn't overlap with anyone else's's area of expertise.
Cool ;-)
To make this easier, I think it better to split this up into smaller
pieces. For example, you only sel
Does maxima really use emacs as a lisp interpreter, or is it just trying to
install an emacs UI? In any case, I don't think this should be a release
blocker. Please open a ticket!
On Wednesday, December 18, 2013 9:01:14 AM UTC, Martin Raum wrote:
>
> I put that into gdb; the problem seems to or
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
Hi Volker,
On 2013-12-18, Volker Braun wrote:
> This is the first official release for Sage 6, which from now on will use
> git and a single unified repository.
Congratulation!
> * The master branch will stay at 6.0 until 6.1 is released
> * The develop branch will soon move on to 6.1.beta0
D
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
On Wednesday, December 18, 2013 11:09:36 AM UTC, Simon King wrote:
>
> > * The master branch will stay at 6.0 until 6.1 is released
> > * The develop branch will soon move on to 6.1.beta0
> Does this mean that for doing development work on trac, one should
> henceforth do "git checkout trac deve
I'd like to do some of this too, although I'm not very clear on how it
would be organized -- would I look at the list of tickets, pick some,
and send a sketch or draft announcement to sage-marketing? Could
people who've been working on closing a big ticket send us an
announcement? Would we organi
On Wed, Dec 18, 2013 at 3:27 PM, Niles Johnson wrote:
> I'd like to do some of this too, although I'm not very clear on how it
> would be organized
good question.
in the spirit of "dogfeeding" us our own stuff, we could start to
collaborate at cloud.sagemath.org. everyone who wants to do this, d
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
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
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:
>
>
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
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
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
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
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
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
[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-
--
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
21 matches
Mail list logo
