On Wed, Sep 11, 2019 at 4:09 PM Mariel Supina
wrote:
>
>
>
> On Wednesday, September 11, 2019 at 12:18:37 PM UTC+2, Dima Pasechnik wrote:
>>
>> OK, thanks, let's do more debugging of cypari:
>>
>>cd /srv/public/shared/sage/upstream
>>tar xf cypari2-2.1.1.tar.gz
>>cd cypari2-2.1.1/
>>
On Wednesday, September 11, 2019 at 12:18:37 PM UTC+2, Dima Pasechnik wrote:
>
> OK, thanks, let's do more debugging of cypari:
>
>cd /srv/public/shared/sage/upstream
>tar xf cypari2-2.1.1.tar.gz
>cd cypari2-2.1.1/
>
> now, start Sage's Python:
>
>../../sage -python
>
>
OK, thanks, let's do more debugging of cypari:
cd /srv/public/shared/sage/upstream
tar xf cypari2-2.1.1.tar.gz
cd cypari2-2.1.1/
now, start Sage's Python:
../../sage -python
and at its prompt, do
import autogen
autogen.pari_share()
Post the result of the last 3 commands.
On Tue, Sep 10, 2019 at 5:30 PM Mariel Supina
wrote:
>
> On Tuesday, September 10, 2019 at 5:50:53 PM UTC+2, Dima Pasechnik wrote:
>>
>> Thanks. OK, I see that you're supposed to be building Pari, anyway,
>> amd then the rest should have worked. Strange.
>>
>> To make sure bulding Pari worked,
On Tuesday, September 10, 2019 at 5:50:53 PM UTC+2, Dima Pasechnik wrote:
>
> Thanks. OK, I see that you're supposed to be building Pari, anyway,
> amd then the rest should have worked. Strange.
>
> To make sure bulding Pari worked, could you do the following:
> In the directory you're
Thanks. OK, I see that you're supposed to be building Pari, anyway,
amd then the rest should have worked. Strange.
To make sure bulding Pari worked, could you do the following:
In the directory you're building Sage, run
./sage --gp --version
and post the output. Also, please post the output
I have attached the output of ./configure --with-python=3.
On Tuesday, September 10, 2019 at 3:53:06 PM UTC+2, Dima Pasechnik wrote:
> On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
> > wrote:
> >
> > Hi,
> >
> > On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik
> wrote:
>
On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
wrote:
>
> Hi,
>
> On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>>
>> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
>> wrote:
>> >
>> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The
>> > problem
On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
wrote:
>
> Hi,
>
> On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>>
>> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
>> wrote:
>> >
>> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The
>> > problem
Hi,
On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>
> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
> > wrote:
> >
> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The
> problem is in the package "cypari", the relevant log is attached:
>
>
On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
wrote:
>
> On Debian stretch, I get a compilation error making sage 8.9.beta9. The
> problem is in the package "cypari", the relevant log is attached:
Are you upgrading? Building from scratch?
The interesting line is
error: [Errno 2] No such file
On Debian stretch, I get a compilation error making sage 8.9.beta9. The
problem is in the package "cypari", the relevant log is attached:
Found local metadata for cypari-2.1.1
Attempting to download package cypari2-2.1.1.tar.gz from mirrors
On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:
*- python2: *
- incremental build (from 8.9.beta8, with -j16) OK
- all tests from ptestlong passed
-
*python3: *
- incremental build (from 8.9.beta8, with -j16) OK
- tests from ptest-python3 passed, except for
Running ptestlong with few optional + external packages including
Using
--optional=awali,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
I obtain:
With a Python 3 build on OS X, I get a sporadic failure in
numerical/linear_tensor_element.pyx — it fails not every time, but at least
half the time. As far as I can tell, this is due to #27587 (that is, I get
failures with 8.9.beta8 + that ticket, but not with 8.9.beta8), but I don't
On another maciine (Debian testing running on core i7 + 16 GB RAM),
upgrading a Python 3-based Sage 8.9.beta8 to beta9 gives me the same
permanent failure of prest-python3, pl;us another (also already reported):
charpent@zen-book-flip:/usr/local/sage-P3-2$ sage -t --long --warn-long
157.5
On Debian testing running on core i5 + 8 GB RAM, upgrading a Python 3-based
Sage 8.9.beta8 to beta9 gives me one permanent failure of prest-python3,
already multireported:
charpent@p-202-021:/usr/local/sage-python3$ sage -t --long
src/sage/rings/polynomial/polynomial_rational_flint.pyx
too
17 matches
Mail list logo
