http://build.sagedev.org/release/waterfall
On Friday, November 20, 2015 at 10:35:25 AM UTC-5, kcrisman wrote:
>
> Volker, what are our current auto-build frameworks?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this grou
Hi all,
We discovered that MPIR-2.7.1 caused many systems to complain of missing
symbols (and other systems to be silently broken).
The reason was MPIR-2.7.0 had a broken .so version number, so the linker
considered MPIR-2.7.1 to be a downgrade compared to MPIR-2.7.0 (or other
versions of GMP etc
Well, 30s ago I reissued 2.7.1.
I will now try to issue 2.7.2. But it may cause additional issues. Changing
the version number is a massively complicated job. Another massively
entertaining facepalm.
Bill.
On 20 November 2015 at 19:23, Jeroen Demeyer wrote:
> On 2015-11-20 17:06, 'Bill Hart' v
On 2015-11-20 17:06, 'Bill Hart' via mpir-devel wrote:
The only question is, do you want me to release MPIR-2.7.2 for this or
reissue MPIR-2.7.1?
I don't think you can "reissue" MPIR-2.7.1. Make it MPIR-2.7.2.
--
You received this message because you are subscribed to the Google Groups
"sage-
On Thursday, 19 November 2015 17:37:12 UTC, Bill Hart wrote:
>
> You can understand my confusion then, as in MPIR 2.7.0 we had:
>
> LIBGMP_LT_CURRENT = 16
> LIBGMP_LT_REVISION = 0
> LIBGMP_LT_AGE = 6
>
> and in MPIR-2.7.1 we have:
>
> LIBGMP_LT_CURRENT = 16
> LIBGMP_LT_REVISION = 1
> LIBGMP_LT_A
We have actually hit this problem ourselves and are quite frankly mystified
as to where it is picking up a broken MPIR or GMP from...
Anyway, I propose the following solution. If we change the numbers in
Makefile.am to 22 : 6 : 1 we should get a library version number 16.6.1
which should exceed al
>
>
>
> He told me that the members of INRIA and CNRS (there are several such
> guys among us) had access to a continuous integration service using a
> pool of machines hosted in another research center. He also told me
> that all was done through virtual machines, and that we could chose
> im
we now have a permission from Brinkmann to release his part of the code
under whatever license we see fit;
we already obtained a permission from from Brendan McKay to release nauty
as a GPLed Sage package, so we
are all set for this to go ahead.
-
On 2015-11-19 19:03, Luca Sodomaco wrote:
Hi,
I'm a Master Student in Mathematics from University of Trieste, Italy,
and today I was trying to compile Sage on my laptop. Unfortunately the
compilation stopped and it seems that the problems involve the package
git-2.3.0. Below I report a brief desc
On 2015-11-20 13:11, James Cruickshank wrote:
Hi,
First time poster. I have run into the same problem as the OP, so I
wonder if there is an update to this
Generally, one cannot "just" run Sage's Python and hope that everything
works. There is various environment variables which need to be set
Hi,
First time poster. I have run into the same problem as the OP, so I wonder
if there is an update to this
I pretty much came up against all the same problems, although I configured
apache slightly differently to use the
sage version python - I set it up so that Django is run in daemon mode,
Hello everybody,
I just had a chat with an engineer from INRIA Sophia Antipolis (where
David Coudert also works).
He told me that the members of INRIA and CNRS (there are several such
guys among us) had access to a continuous integration service using a
pool of machines hosted in another research
Hi Luca,
On 2015-11-20, Luca Sodomaco wrote:
> Yes I have SAGE_CHECK turned on, I can disable it. I have system-wide git
> installed, version 2.6.2. Is it enough? Is it sufficient if I restart
> compilation again by typing 'make' with SAGE_CHECK empty? Or I need more
> options?
Normally, doing '
Nathann Cohen wrote:
> All I can come up with is something like a 'warning', a message that
> would show up once per session, when triggered by a computation. I'm
> all ears for any way to tell users things they didn't know they
> needed.
I'd simply use the Python logging module and introduce a ne
Yes I have SAGE_CHECK turned on, I can disable it. I have system-wide git
installed, version 2.6.2. Is it enough? Is it sufficient if I restart
compilation again by typing 'make' with SAGE_CHECK empty? Or I need more
options?
Thanks
2015-11-19 19:29 GMT+01:00 Dima Pasechnik :
>
>
> On Thursday, 1
15 matches
Mail list logo
