Volker Braun wrote:
vbraun@boxen:~/release/sage-6.2.beta4$ md5 sage-6.2.beta4.tar.gz
The program 'md5' is currently not installed. You can install it by typing:
sudo apt-get install sleuthkit
-bash: md5: command not found
leif@boxen:~$ md5sum /home/release/sage-6.2.beta4/sage-6.2.beta4
with install_name and the old Darwin linker) here, but
that's really just a blind guess...
(For eclib at least, the symlinks appear to get set up correctly.
Haven't looked at the FLINT build logs.)
-leif
Can you build with SAGE_CHECK='yes' so that
it will run eclib's own tests?
Of course
http://trac.sagemath.org/ticket/16017 - John, any thoughts? (Or
Leif or JP?)
Well, since it is illogical ;-) , we should make the addition
platform-dependent (apparently MacOS X 10.4 / Darwin 8 only, not Darwin
in general, and presumably Cygwin as well).
But someone familiar with flat vs. two
probably annoying the user). The changes in 3.81 suppress
them, but do not change the behaviour w.r.t. '[-]include' and *empty*
include file lists; they mainly deal with how 'make' behaves if the
files to include don't exist and/or cannot be remade (according to [1]
and [2] at least).
-leif
[1
François Bissey wrote:
On Thu, 27 Mar 2014 20:29:29 leif wrote:
kcrisman wrote:
On Thursday, March 27, 2014 1:29:58 PM UTC-4, kcrisman wrote:
eclib's test suite passed without errors
That sounds good -- you must therefore have a working version of
mwrank (and what
...
spkg-check: Running test_buildexamples.py...
Traceback (most recent call last):
File /Users/leif/Sage/sage-6.2.beta5/local/bin/dot2tex, line 2, in
module
from dot2tex.dot2tex import main
File
/Users/leif
On 29.03.2014 20:49, leif wrote:
Ben Salisbury wrote:
Hi all,
It seems that my dot2tex no longer functions after upgrading to
6.2.beta5.
sage: C = crystals.Tableaux(B2,shape=[2,1])
sage: view(C)
dot2tex not available. Install after running 'sage -sh'
I attempted to force a reinstallation
) 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
leif wrote:
Volker Braun wrote:
make distclean make
OMG, Sage's new Ctrl-Alt-Del?
'./sage -ba-force' should be sufficient (only rebuilds the whole Sage
library from scratch).
(after upgrading and having run 'make' of course)
-leif
The reason is that NTL got upgraded, and apparently
Volker Braun wrote:
It builds fine on bsd with 10.6. Maybe you need to update your XCode?
I guess his libtool in PATH is simply not Apple's...
So presumably an upstream bug.
-leif
On Thursday, April 10, 2014 3:04:37 PM UTC+2, Dima Pasechnik wrote:
I am stuck on singular on OSX 10.6.8
?
-leif
sage -t --long src/sage/interfaces/ecm.py
**
File src/sage/interfaces/ecm.py, line 452, in
sage.interfaces.ecm.ECM.one_curve
Failed example:
f.one_curve(n, B1=50, algorithm=P-1)
Exception raised:
Traceback
Andrey Novoseltsev wrote:
On Tuesday, 15 April 2014 17:57:33 UTC-6, leif wrote:
Andrey Novoseltsev wrote:
I am getting new ecm errors on Opteron 6272/Debian (not sure how
new, I
was not compiling Sage on this machine for a while):
Could you run GMP-ECM's test suite
that this ticket is in beta8 (I think). You probably
need a bit
of make distclean make
Or just './sage -ba-force' to rebuild the whole Sage library.
-leif
On 17/04/2014, at 22:54, John Cremona john.crem...@gmail.com wrote:
This is a different problem to the one I reported on the other
sage-release
leif wrote:
Francois Bissey wrote:
sage/matrix/matrix_mpolynomial_dense.so
that's who. In this case it hasn't been rebuild after ntl's upgrade.
Weird, since Jeroen made every extension module also depend on
src/setup.py, and that definitely changed...
Jean-Pierre
is probably right except
).
-leif
--
() 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
-spkg; 'make'
already has '-t', but I don't know whether that works from the
top-level) to touch the file regardless of whether it really got
rebuilt/reinstalled; one can of course always fake manually (although
that might get tedious for many, probably all dependent, packages).
-leif
Andrey Novoseltsev wrote:
On Sunday, 27 April 2014 09:31:13 UTC-6, leif wrote:
Tracking this further down...
Would you mind retrying whether
env CFLAGS=-O3 -march=native -mtune=native ./sage -f -c ecm
also works for you?
It does not:
Ah, thanks, but I just noticed
. Siehe 'git --help'.
Haben Sie das gemeint?
shell
So, both beta0 and beta1 are broken because of the git shipped by
Sage.
Slightly related,
sage --sh -c 'git help foo'
doesn't give Sage's, but the system-wide git's manpage on git-foo (if
present).
-leif
--
() The ASCII Ribbon
make it the default in the top-level Makefile has been
discussed a couple of times in the past years, and IIRC most agreed we
should do so, but so far even 'sudo open a ticket' failed.
-leif
__
* aka $SAGE_RC_FILE, sourced by sage-env if present
--
() The ASCII Ribbon Campaign
/\ Help
be called;
'quick-and-dirty-upgrade-not-really-rebuilding-dependent-packages'
perhaps, or 'unsafe-rebuild'.)
Documentation needs to get updated accordingly as well of course
(presumably the main obstacle).
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received
isn't the same as 'sage --upgrade'.
-leif
--
() 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
P Purkayastha wrote:
On Monday, May 26, 2014 10:08:19 PM UTC+8, leif wrote:
Nathann Cohen wrote:
Whether we should make it the default in the top-level Makefile
has been
discussed a couple of times in the past years, and IIRC most
agreed we
should do so, but so far
decade, before we introduced SAGE_UPGRADING, which nowadays
more or less just tells 'sage-spkg' to not answer package foo is
already installed. 'make' and our dependencies take care that
'sage-spkg' is called on every dependent package.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure
.)
-leif
--
() 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
/folders/k8/nj0z1bkd11dcs1v5hbh_tknc92p43w/T/sphinx-err-LRSqym.log, if you
want to report the issue to the developers.
That's exactly the bug I had ! I was advised to run this :
sage -f ecl sage -f maxima sage -b
Reinstalling just Maxima suffices.
-leif
--
() The ASCII Ribbon Campaign
/packages/upstream/configure/configure-33.tar.gz
and extract the tarball in $SAGE_ROOT (or just the two [to four] missing
files in config/), then retry 'sage -i ecl'.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed
rerunning them separately?
How many threads on how many cores? Enough memory? Does the order
matter? (You can delete or rename the timings from previous runs since
these usually just worsen the situation; $DOT_SAGE/timings*.json IIRC.)
-leif
Here is a sample of the output from make
/sage-6.3.beta6.tar.gz
-leif
--
() 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
is misconfigured (in your ssh session?)... ;-)
Unsetting DISPLAY may suffice.
-leif
The sage install has created
$SAGE_ROOT/local/lib/python2.7/site-packages/matplotlib-1.3.1-py2.7-linux-x86_64.egg/matplotlib/mpl-data/matplotlibrc
which sets the backend to tkagg. I tried copying that file
of Singular know too much
about FLINT's speed, hence fail to locate it [1].
-leif
[1] http://xkcd.com/824/
On 2/08/2014, at 21:52, Francois Bissey francois.bis...@canterbury.ac.nz
wrote:
Hum... some configuration has gone bad on two fronts:
g++ -O2 -g -fPIC -I.. -I/Users/kabel/sage/sage/local
Volker Braun wrote:
IMHO everything should be configured with --enable-shared
--disable-static...
I *knew* you'd take the bait B)
-leif
On Saturday, August 2, 2014 6:06:14 AM UTC-4, leif wrote:
Francois Bissey wrote:
Hum... some configuration has gone bad on two fronts
to me. Do you
need something to happen from other people, which is holding up 6.3?
sudo chown -R vbraun /home/release
sudo chgrp -R release /home/release
or simply
sudo chown -R vbraun:release /home/release
;-)
-leif
For SageMathCloud, I just went ahead and pushed out beta6 of sage-6.3
it's not that easy to add the appropriate flags
there.
Is there a way to force the sage installation not to use the globally
installed versions?
It shouldn't at all. You could move or remove them temporarily though.
-leif
Am Samstag, 2. August 2014 12:55:12 UTC+2 schrieb François
recent GCC version default to -std=gnu99 anyway?
-leif
--
() 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
leif wrote:
Volker Braun wrote:
The configure output is probably the interesting part, Harald.
FWIW, I'm having
checking for gcc-4.9.1 option to accept ISO C99... -std=gnu99
checking for gcc-4.9.1 -std=gnu99 option to accept ISO Standard C...
(cached) -std=gnu99
in the R build log
-scratch on the same machine ?
Well, you can use SAGE_ATLAS_ARCH to give ATLAS some hints.
And you could save the libraries somewhere outside the Sage tree and use
SAGE_ATLAS_LIB later on. Unfortunately there's still no script to do
that, AFAIK.
-leif
--
() The ASCII Ribbon Campaign
/\ Help
probably need a release announcement candidate as well. ;-)
FWIW, I occassionally correct spellings on tickets when I see them (just
like Karl-Dieter and others do or did). But we also no longer have
author and reviewer names in the pre-release (beta/rc) announcements.
-leif
--
() The ASCII
tell, *all* mirrors are outdated, at least w.r.t. the
devel tarball.)
-leif
[1] http://sagemath.org/download-latest.html
--
() 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
On 20.08.2014 14:09, leif wrote:
On 20.08.2014 14:01, Jean-Pierre Flori wrote:
It seems that the tarball for the devel sources is very outdated on
mirrors (at least the french and chinese ones).
Well,
The latest development version is 6.1.beta1 released on 2013-12-21. [1]
I already noted
].
And FWIW, in most cases *nix systems aren't affected; M$ and Apple in
contrast are.
-leif
[1] https://launchpad.net/ubuntu/+source/git/1:1.9.1-1ubuntu0.1
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop
On 02/19/2015 12:27 AM, Volker Braun wrote:
The 6.5 binaries that built successfully are now on the mirror.
[...]
Linux 32-bit (including the VM) failed because of
http://trac.sagemath.org/ticket/17806
Meanwhile needs review...
-leif
--
You received this message because you
On 04/21/2015 05:02 PM, Volker Braun wrote:
The source tarball will appear at one point at
http://files.sagemath.org/devel/ (Harald: can you upload it there?)
For the impatient:
http://boxen.math.washington.edu/home/release/sage-6.7.beta2.tar.gz
still works.
-leif
Or get the develop git
, ... Authors, ... Group, ... Team, ... ?
Task force.
-leif
--
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
noticed that in
src/sage/structure/sage_object.pyx
two (actually just one, the second a consequence) doctests fail in case
FFLAGS happen to be set (and don't contain -fPIC).
Otherwise all tests (ptestlong) passed on Ubuntu 10.04.4 x86_64 (with
GCC 4.4.3; '-O3' and native).
-leif
--
You
leif wrote:
Sébastien Labbé wrote:
On Ubuntu 14.04 64 bit, after make distclean, make ptestlong finishes with:
--
All tests passed!
--
Not sure how old
...
-leif
[1]
http://sagemath.org/doc/installation/source.html#linux-prerequisite-installation
[2] http://trac.sagemath.org/ticket/18382
--
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
though.
-leif
--
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
configure-$CONFVERSION.tar.gz
failed
-leif
P.S.: I mentioned on the ticket I had not yet tested it thoroughly, but
someone else gave it positive review... ;-)
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group
]: *** Warte auf noch nicht beendete Prozesse...
ROFL, reviewing/merging #15642 that is.
You can safely pull the branch there, then using a mirror.
Or download the upstream tarballs manually from a mirror (they're in
spkg/upstream/, not packages/upstream/).
-leif
--
You received this message because
Dima Pasechnik wrote:
On Wednesday, 13 May 2015 18:32:58 UTC+1, Rob Beezer wrote:
Rebuilding on SageMathCloud due to change of underlying hardware
(now Intel Haskell).
Wow, lazy functional hardware from Intel!
No, neither functional nor lazy, just spiced with curry.
-leif
packages. (It probably will again in the future, but the site is
currently moving.)
-leif
--
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
-lasting bug in
the Makefile):
http://trac.sagemath.org/ticket/18424
(Trivial to fix, two possible patches up there.)
This bug made it even into Sage 6.6 without anybody noticing, so we
probably have to tweak our (final) testing procedures, at least on the bots.
-leif
--
You received
Harald Schilly wrote:
Looks good to me, at least the numbers make sense.
The numbers. But Teewurst in NYC? Really? 8-)
-leif
--
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
leif wrote:
kcrisman wrote:
I have a student on OS X who is getting a weird build error with libgd -
missing ft2build.h header. Could this be related to the recent upgrade
to libgd? However, he needs to use the most recent Sage devel version
because he has the latest Xcode.
Post the full
kcrisman wrote:
I have a student on OS X who is getting a weird build error with libgd -
missing ft2build.h header. Could this be related to the recent upgrade
to libgd? However, he needs to use the most recent Sage devel version
because he has the latest Xcode.
Post the full log.
-leif
-edit it, or do
$ touch local/lib/sage-force-relocate.txt
$ ./sage --sh -c sage-location
(Afterwards, run 'make' again and wait for the next error... ;-) )
-leif
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group
and lacked important security fixes.
-leif
--
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
there is a
separate folder for compiling Sage code.
They were in the .gitignore before but the ticket that moved them also
remove the ignore entries for the old file locations.
-leif
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from
cent said, the problem was probably the typo
> "docclean" instead of "doc-clean", nothing more.
While 'make docclean' should have spit out an error message, but she
probably didn't notice.
In any case, it was certainly not related to "razor-sharp edges of the
Volker Braun wrote:
> With Sage-6.8 is pretty much the same, maybe ~< 10% less memory usage;
> In any case no drastic change.
Just about 50+% increase in build time...? ;-)
-leif
For reference: The figures for 6.9.rc0:
https://lh3.googleusercontent.com/-fvz6bvxGrVo/Vgaae7pRfgI/AA
Andrey Novoseltsev wrote:
> Not sure if has surfaced already, but after make distclean the build
> with tests fails at
>
> ...
> Running the test suite for gf2x-1.1.p1...
Which version of GCC, CPU?
-leif
> make[3]: Entering directory
> '/home/novoselt/sage/local/var/tmp/s
leif wrote:
> Volker Braun wrote:
>> 8400a23 Updated Sage version to 6.10.beta6
>
> Besides the usual doctest failure*, I'm getting new numerical noise in
> beta6:
>
> sage -t --long --warn-long 60.9 src/sage/matrix
--
sage -t --long --warn-long 60.1 src/sage/symbolic/expression.pyx # 1
doctest failed
--
-leif
> 6270d3b Trac #19658: update sympy 0.7.6 -> 0.7.6.1
> 81a80a8 Trac #19312: Update
HG wrote:
> Leif sorry, I don't know what you mean :
> Do I have to type your proc in a shell ?
Nope, it was just a suggestion to slightly change our "top-level" error
messages (and not /that/ seriously meant either).
-leif
--
You received this message because you are subscrib
INSTALL_GCC=yes AFAIK, so Sage is mainly built with GCC 4.9.2 which
ships with an older libstdc++.
The issue will presumably vanish when we get rid of setting
LD_LIBRARY_PATH (and using sage-native-execute here and there); until
then, you can simply create symlinks to your distro's libstdc++,
libgfortra
Henri Girard wrote:
> 6.9 or 6.10 ?
6.10 of course; see http://git.sagemath.org/sage.git/
-leif
> Le 18/12/2015 20:18, Volker Braun a écrit :
>> The "master" git branch has been updated to Sage-6.9. As always, you
>> can get the latest beta version f
rd package (despite the comments on that the same ticket, #14405,
removed from spkg-install).
Just saying...
-leif
> I'm guessing this causes us to
> pick up the versioned symbol names from the system libtinfo:
>
> gcc -shared -Wl,-soname,libreadline.so.6.3
> -Wl,-rpath,/home/vbr
leif wrote:
> Francois Bissey wrote:
>>> __
>>> *
>>> sage -t --long --warn-long 60.9 src/sage/symbolic/expression.pyx
>>> **
>>> Fil
failure, 1.65 s]
--
sage -t --long --warn-long 60.9 src/sage/matrix/matrix_double_dense.pyx
# 1 doctest failed
--
(Linux on a Haswell, GCC 5.1.0)
-leif
__
*
sage -t --long --warn-long 60.9 src/sage/symboli
Francois Bissey wrote:
>
>> On 29/11/2015, at 08:16, leif <not.rea...@online.de> wrote:
>>
>> Volker Braun wrote:
>>> 8400a23 Updated Sage version to 6.10.beta6
>>
>> Besides the usual doctest failure*, I'm getting new numerical noise in
>>
So far I've successfully built Sage 7.2 with GCC 6.1 and the above
changes, except for some Sage library modules which include LinBox
headers, and hence have to be built with '-std=gnu++98', too.
-leif
>
> François
>
>> On 19/06/2016, at 00:37, leif <not.rea...@online.de> wrote
press Ctrl-C, I don't know it).
-leif
> On Saturday, June 18, 2016 at 2:53:51 AM UTC+2, kcrisman wrote:
>
> Had to make distclean && make but it had an awful long time setting
> up build directory for gcc (prior stuff did fine) and then after
> interrupting (
-std=gnu++98 flag. So I don't understand this error.
This might be related to what Singular does with gmp.h, cf. #14737.
-leif
>
> Best,
> Johan
>
>
>
>
> Florent Hivert writes:
>
>> Dear Vorlker,
>>
>> On Mon, Jun 06, 2016 at 06:18:12AM -0
roblem could
> have been?
No idea, but if you delete the GAP workspaces (in $DOT_SAGE/gap/), the
test takes orders of magnitude longer... :-)
-leif
>
> (Tested on Linux Mint 17.3)
>
--
You received this message because you are subscribed to the Google Groups
"sage-re
leif wrote:
> Daniel Krenn wrote:
>> On 2016-07-28 23:39, Volker Braun wrote:
>>> As always, you can get the latest beta version from the "develop" git
>>> branch. Alternatively, the self-contained source tarball is at
>>> http://www.sagemath.org/do
leif wrote:
> leif wrote:
>> Benjamin Hackl wrote:
>>> I have a very similar setup (gcc 6.1.1 20160602 on Arch Linux), and I'm
>>> struggling quite hard to build 7.2:
>>>
>> [SNIP]
>>
>>> The next failure then occurs when the Sage library mo
nately, the reason for this is not that obvious to me---does
> anyone have an idea or suggestions (besides downgrading my gcc...)? :-|
No idea. (All I can see is that it happens early when trying to
initialize libsingular.)
-leif
>
> Benjamin
--
You received this message because you are
ynac.so.2'
to see how the needed libraries are resolved in the Sage environment.
But now it's too late, unless someone wants to retry (without having
Sage's giac already installed)...
(The current solution on #20916 is a temporary work-around, namely to
simply disable the use of giac in Sage's pyn
leif wrote:
> Jean-Pierre Flori wrote:
>> On a POWER7 machine I get an error while building the docs I get a
>> ZeroDivisionError in the plotting section.
>> Did anybody experience it? Do we have a ticket for that?
>
> sudo revive skynet
>
> The only one I'm aw
on POWER
is fbissey, so the answer to both is presumably "no".
-leif
--
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
tional=database_gap,mpir,python2,sage,sage_mode
> Doctesting 1 file.
> sage -t --long --warn-long 98.4 src/sage/homology/simplicial_complex.py
> [588 tests, 6.59 s]
> --
> All tests passed!
> ----
body going to investigate the issue(s)? (See also my other replies.)
-leif
> On Thursday, August 18, 2016 at 6:52:26 AM UTC+2, pipedream wrote:
>
> Hi
>
> On 10 August 2016 at 08:09, Jan Groenewald <j...@aims.ac.za
> > wrote:
>
> Hi
>
>
Jan Groenewald wrote:
> Hi
>
> On 20 August 2016 at 19:36, Harald Schilly <harald.schi...@gmail.com
> <mailto:harald.schi...@gmail.com>> wrote:
>
> On Sat, Aug 20, 2016 at 4:40 PM, leif <not.rea...@online.de
> <mailto:not.rea...@online.de>>
hich
*always* fails in ptestlong, passes when rerun separately), now all
tests pass for me on Linux x86_64 (Haswell-EP; with Sage's GCC 4.9.3).
Thanks!
-leif
> 7b1b3ec Updated SageMath version to 7.4.beta1
> 3f3bfb1 Trac #21245: again some typos
> aeb555a Trac #21241: faq-usage typo 'preparse' sho
larly check the size of ~/.sage/... (or $DOT_SAGE) and clean up
manually, just like for dozens of left-over temporary files from
building and testing.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
/sage/local/lib/python/subprocess.py", line
>> 710, in __init__
>> [sagelib-7.4.beta2] errread, errwrite)
>> [sagelib-7.4.beta2] File
>> "/home/agag/sbrandhorst/sage/sage/local/lib/python/subprocess.py", line
>> 1335, in _execute_child
>> [sagelib-7.
leif wrote:
> From sage-devel (see also my reply there):
>
>>> [sagelib-7.4.beta2] Building interpreters for fast_callable
>>> [sagelib-7.4.beta2] python -u setup.py install
>>> [sagelib-7.4.beta2]
>>> *
leif wrote:
> Volker Braun wrote:
>> 5cd62cb Updated SageMath version to 7.4.beta2
>
> Built from scratch (source tarball), Linux x86_64 (Haswells).
>
> With GCC 6.1.0:
>
> --
> sa
rently belong to different packages.)
And I don't have them on every machine.
-leif
> Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip
> 004018
> 1f sp 7ffce9d03520 error 4 in gentourng[40+19000]
> Aug 30 17:03:54 ark kernel: gentourng[20347]:
leif wrote:
> Francois Bissey wrote:
>>
>>> On 18/08/2016, at 19:38, Francois Bissey <francois.bis...@canterbury.ac.nz>
>>> wrote:
>>>
>>> Stack smashing on 32bits
>>> [dochtml] Setting permissions of DOT_SAGE directory so only you
leif wrote:
> leif wrote:
>> Francois Bissey wrote:
>>>
>>>> On 18/08/2016, at 19:38, Francois Bissey
>>>> <francois.bis...@canterbury.ac.nz> wrote:
>>>>
>>>> Stack smashing on 32bits
>>>> [dochtml] Setting perm
-
Total time for all tests: 956.8 seconds
cpu time: 13.8 seconds
cumulative wall time: 956.7 seconds
real15m59.486s
user12m9.160s
sys 3m56.850s
There's a Python process doing almost nothing most of the time...
-leif
--
You received this message because you
leif wrote:
> Steven Trogdon wrote:
>> I have the following failure:
>>
>> sage: P = graphs.PetersenGraph() ## line 539 ##
>> sage: P.tutte_polynomial() ## line 540 ##
>> x^9 + 6*x^8 + 21*x^7 + 56*x^6 + 12*x^5*y + y^6 + 114*x^5 + 70*x^4*y +
>> 30*x^3*y^2 +
raph on 2 vertices, {'a': 1, 'b': 0})
... which shows that
a) the test doesn't make sense (after all, it's supposed to just test
the deprecation of "certify" I think)
b) as is, the representation returned for a vertex-labeled graph isn't
canonical... ;-)
-leif
P.S.: File src/sage/gra
p.pyx
Bad exit: 2
**
Tests run before process (pid=5609) failed:
sage: a = libgap(10) ## line 11 ##
**
-leif
[1] https://trac.sagemath.org/ticket/15585
--
-b' after changing the file, or just change
$SAGE_LOCAL/lib/python/site-packages/sage/misc/package.py temporarily.)
A branch doing a bit more can be found on #21291 [1].
The main issue is of course still that is_package_installed() gets
called far too often. (There are meanwhile tickets addres
96 matches
Mail list logo
