Sage 9.1.beta2 released

188 views
Skip to first unread message

Volker Braun

unread,
Jan 27, 2020, 6:04:20 PM1/27/20
to sage-release
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/download-latest.html 


2cbd93e0b7 (tag: 9.1.beta2, trac/develop) Updated SageMath version to 9.1.beta2
fb9218e13b Trac #29072: unused import cleaning ticket (partial)
7cec05e0c7 Trac #28755: "The following package(s) may have failed to build": Improve output
bb5110ca19 Trac #27315: Minor optimizations to libsingular polynomials
18389bdd76 Trac #29070: Queer tableaux for B(-infinity) and B(lambda)
bdfebfb180 Trac #29069: Fix broken link in crystals catalog
96695b33cf Trac #29068: little cleanup of imports and tweak again .lgtm.yml
4da45e2169 Trac #29067: Make ./configure --help a bit shorter by combining --with-system-SPKG and --with-system-SPK=force
1c5d011b5f Trac #29038: Python package sage_conf: Provides optional configuration information for sagelib
9cf951e6ea Trac #29007: faster permutation conversions between GAP and Sage
aff7f32ac2 Trac #28247: Parametrize the cube/hypercube functions in the library of polytopes
0d63d6e276 Trac #21413: A class for ring extensions
349a5ab632 Trac #29044: Add default warnings filters in a Python debug build
7de6a929a5 Trac #29046: Minor improvements in sage.rings.number_field.galois_group
35411d34b1 Trac #29011: speed up number field element conversions
10ad03d047 Trac #28787: _add_ method for tensors with indices
1a1e1a0935 Trac #4618: Puiseux series
3c92cbc37c Trac #29063: spkg-configure.m4 for planarity
229d4365d8 Trac #29057: make stack method of Polyhedron use fraction_field
ed23ee3c7d Trac #29049: partially reverse the logic of py2 / py3 doctest fixing
788a2d642f Trac #29048: 1 doctest failing in src/sage/databases/oeis.py with tag internet
3dcf55bec6 Trac #29047: 1 internet doctest failing in repl/load.py
fcc768db49 Trac #28989: Bug in proper cycles of indefinite binary quadratic forms
f1dc86f78b Trac #29026: update m4ri(e) to Jan 2020 versions
3d8399c96a Trac #29035: some details in free pre-Lie algebras
3f9ef468a2 Trac #29002: spkg-configure.m4 for sqlite
59f6a83618 Trac #28999: qepcad interface is broken with python3
c10179b2eb Trac #28996: Have `implementation='NTL'` work for series over ZZ
44345faf0b Trac #28616: CombinatorialFace: replace Vrepr() and Hrepr() by more consistent names
3deaa0a61a Trac #28385: tides does not pass self-tests on 32bit system
dde78cbd22 (tag: 9.1.beta1) Updated SageMath version to 9.1.beta1

Eric Gourgoulhon

unread,
Jan 28, 2020, 5:45:59 AM1/28/20
to sage-release
On Ubuntu 18.04 running on a bi-Xeon E5-2623 (8 cores) + 16 GB RAM computer:

  - incremental build (with -j16) from 9.1.beta1: OK
  - all tests from ptestlong passed

Eric

Emmanuel Charpentier

unread,
Jan 28, 2020, 10:15:21 AM1/28/20
to sage-release
On Debian testing running on core I5 + 8 GB RAM, upgrading from Python 3-based 9.1.beta1 to 9.1.beta2:
  • passes ptestlong without failure;
  • does NOT pass ptestalllong, which gets interrupted by multiple failures while doctesting findstat.py : see attached ptestalllong.log.
I had similar failures with 9.1.beta1 on another machine, which I (probably wrongly) ended up attributing to transient networking problems (a repeat attempt succeeded). I'll test 9.1.beta2 on this second machine. 

HTH;
ptestalllong.log

Emmanuel Charpentier

unread,
Jan 29, 2020, 3:04:23 AM1/29/20
to sage-release

On Debian testing ruinning on core i7 + 16 GB RAM (slightly different installed software ; notably gap_packages is installed), after upgrading a Python 3-base sage 9.1.beta1 to 9.1.beta2:

  • ptestlong gets three permanent failures (already reported multiple
    times) and no transient failure:
File Result P/T
src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P
src/sage/tests/gap_packages.py 1 doctest failed P
src/sage/libs/glpk/error.pyx 1 doctest failed P
  • ptestalllong fails after errors on failstat.py (see attached ptestalllong.py) ; it reports 2310/3814 files tested.:
File Result P/T
src/sage/plot/animate.py 7 doctests failed T
src/sage/symbolic/integration/external.py 1 doctest failed T
src/sage/misc/latex.py 1 doctest failed T
src/sage/tests/gap_packages.py 1 doctest failed P
src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P
src/sage/libs/glpk/error.pyx 1 doctest failed P

And findstat.py, ran standalone, succeeds.

This is annoying... I have no clue about the source of the problem.

Emmanuel Charpentier

unread,
Jan 29, 2020, 3:06:06 AM1/29/20
to sage-release
Forgot the announced ptestalllong.log...
ptestalllong.log

Markus Wageringel

unread,
Jan 30, 2020, 3:23:34 AM1/30/20
to sage-release
With 9.1.beta2, I frequently see the following transient failure on my patchbot running on CentOS 7.7:

File "src/sage/schemes/elliptic_curves/isogeny_small_degree.py", line 2173, in sage.schemes.elliptic_curves.isogeny_small_degree.isogenies_prime_degree_general
Failed example:
    len
(E.change_ring(GF(3^2,'a')).isogenies_prime_degree(13))
Exception raised:
   
Traceback (most recent call last):
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
       
self.compile_and_execute(example, compiler, test.globs)
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1123, in compile_and_execute
       
exec(compiled, globs)
     
File "<doctest sage.schemes.elliptic_curves.isogeny_small_degree.isogenies_prime_degree_general[22]>", line 1, in <module>
        len
(E.change_ring(GF(Integer(3)**Integer(2),'a')).isogenies_prime_degree(Integer(13)))
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/schemes/elliptic_curves/ell_field.py", line 1092, in isogenies_prime_degree
       
return sum([isogenies_prime_degree(self, d) for d in L], [])
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/schemes/elliptic_curves/ell_field.py", line 1092, in <listcomp>
       
return sum([isogenies_prime_degree(self, d) for d in L], [])
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/schemes/elliptic_curves/isogeny_small_degree.py", line 2360, in isogenies_prime_degree
       
return isogenies_prime_degree_general(E,l, minimal_models=minimal_models)
     
File "/amd/compute/sagebot/sage/local/lib/python3.7/site-packages/sage/schemes/elliptic_curves/isogeny_small_degree.py", line 2249, in isogenies_prime_degree_general
        factors
.remove(f)
   
ValueError: list.remove(x): x not in list

This happens only rarely when testing the file standalone. I have opened #29107 for this.


Also, the directory `build/pkgs/sage_conf/src/` contains untracked autogenerated files. This makes `configure` fail if one tries to checkout a previous beta.

John H Palmieri

unread,
Jan 30, 2020, 2:22:52 PM1/30/20
to sage-release


On Thursday, January 30, 2020 at 12:23:34 AM UTC-8, Markus Wageringel wrote:


Also, the directory `build/pkgs/sage_conf/src/` contains untracked autogenerated files. This makes `configure` fail if one tries to checkout a previous beta.


I see this too. I don't understand why it happens, since the files are listed in `build/pkgs/sage_conf/src/.gitignore`. I suppose when switching brances, this `.gitignore` file gets cleaned up before the autogenerated files, so they are orphans?

Matthias Köppe

unread,
Jan 30, 2020, 6:17:16 PM1/30/20
to sage-release
Yes, when switching branches to one that has not merged 9.1.beta2, one needs to clean up this directory at the moment (rm -rf build/pkgs/sage_conf). The reason is that our current ./configure is a little bit too sensitive to stray files/subdirectories in the build/pkgs directory. I have created ticket #29114 ("Only ./bootstrap should glob build/pkgs") to address this.

Matthias Köppe

unread,
Jan 30, 2020, 6:29:30 PM1/30/20
to sage-release
On Thursday, January 30, 2020 at 3:23:34 AM UTC-5, Markus Wageringel wrote:

Also, the directory `build/pkgs/sage_conf/src/` contains untracked autogenerated files. This makes `configure` fail if one tries to checkout a previous beta.

As a workaround if you have to switch to older branches I would recommend to use a global gitignore file.

Justin C. Walker

unread,
Jan 31, 2020, 12:05:34 AM1/31/20
to sage-r...@googlegroups.com


> On Jan 27, 2020, at 15:04 , Volker Braun <vbrau...@gmail.com> 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/download-latest.html

Built w/o problems from fresh clones of the develop branch, on three macOS systems: 10.13.6 (2017 iMac Pro, 18-core Xeon W), 10.14.6 (2017 MBP, Quad-core Core i7), and 10.15.2 (2019 MBP, 8-core Core i9).

10.13.6: all tests passed!

10.14.6: all tests passed!

10.15.2: all tests passed!

Justin


--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's Income
--
In mathematics you don't understand
things. You just get used to them.
--John von Neumann
--

Emmanuel Charpentier

unread,
Jan 31, 2020, 9:45:18 AM1/31/20
to sage-release
On the same machine, I can't rebuild Sage from scratch (in a different directiory). ./configure + make distclean + make ptestalllong fails at building ECL, which complaints:

gcc -DECLDIR="\"/usr/local/sage-9/local/lib/ecl-16.1.2\"" -I. -I/usr/local/sage-
9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build -I/usr/local/sage-9/local/var
/tmp/sage/build/ecl-16.1.2.p5/src/src/c -I../ecl/gc -DECL_API -DECL_NO_LEGACY   
  -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o ffi.o ffi.o.c
/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/src/c/ffi.d:148:34:
 error: 'FFI_SYSV' undeclared here (not in a function)
  148 |         {@':cdecl', FFI_SYSV},
      |                                  ^       
make[6]: *** [Makefile:86: ffi.o] Error 1
make[6]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.
2.p5/src/build/c'
make[5]: *** [Makefile:119: libeclmin.a] Error 2
make[5]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.
2.p5/src/build'
make[4]: *** [Makefile:70: all] Error 2
make[4]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src'
********************************************************************************
Error building ecl-16.1.2.p5
********************************************************************************

Relevant logs attached.

Le mardi 28 janvier 2020 16:15:21 UTC+1, Emmanuel Charpentier a écrit :
logs.tar.gz

Dima Pasechnik

unread,
Jan 31, 2020, 10:06:12 AM1/31/20
to sage-release
have you updated system's libffi lately?

Could you try

./configure --without-system-libffi
make

?
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/14893264-c655-4932-8b03-be917e5f0892%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 2:17:57 PM1/31/20
to sage-release


Le vendredi 31 janvier 2020 16:06:12 UTC+1, Dima Pasechnik a écrit :
have you updated system's libffi lately?

Possibly: I follow Debian testing, but do not look closely each and every upgrade. Currently, I have :

charpent@zen-book-flip:/usr/local/sage-9$ dpkg -l "libffi*" | cat
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom              Version      Architecture Description
+++-================-============-============-======================================================
ii  libffi-dev:amd64 3.3-3        amd64        Foreign Function Interface library (development files)
un  libffi4-dev      <aucune>     <aucune>     (aucune description n'est disponible)
ii  libffi6:amd64    3.2.1-9      amd64        Foreign Function Interface library runtime
ii  libffi6:i386     3.2.1-9      i386         Foreign Function Interface library runtime
ii  libffi7:amd64    3.3-3        amd64        Foreign Function Interface library runtime
ii  libffi7:i386     3.3-3        i386         Foreign Function Interface library runtime
 
Could you try

./configure --without-system-libffi
make

?

Underway. I'm not optimistic: ecl has been recompiled after reconfiguration, and the log file still ends with :

gcc -DECLDIR="\"/usr/local/sage-9/local/lib/ecl-16.1.2\"" -I. -I/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build -I/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/src/c -I../ecl/gc -DECL_API -DECL_NO_LEGACY     -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o ffi.o ffi.o.c
/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/src/c/ffi.d:148:34: error: 'FFI_SYSV' undeclared here (not in a function)
  148 |         {@':cdecl', FFI_SYSV},
      |                                  ^       
make[6]: *** [Makefile:86: ffi.o] Error 1
make[6]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build/c'
make[5]: *** [Makefile:119: libeclmin.a] Error 2
make[5]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build'
make[4]: *** [Makefile:70: all] Error 2
make[4]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src'
********************************************************************************
Error building ecl-16.1.2.p5
********************************************************************************

I'll keep you posted.
 
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 2:22:27 PM1/31/20
to sage-release
Indeed : make has failed with the same failure as before. To confirm this, I'll distclean and retry, but don't believe it will be successful. Kep you posted.

HTH,

Dima Pasechnik

unread,
Jan 31, 2020, 2:30:39 PM1/31/20
to sage-release
just as a sanity check, please verify that Sage's libffi got built.

On Fri, Jan 31, 2020 at 7:22 PM Emmanuel Charpentier
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/be427777-3869-4e99-82cd-7a8300e91c4f%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 2:37:03 PM1/31/20
to sage-release


Le vendredi 31 janvier 2020 20:30:39 UTC+1, Dima Pasechnik a écrit :
just as a sanity check, please verify that Sage's libffi got built.

It did. No joy.

Currently re-makeing after distclean. Don't hold your breath and have a nice walk...
 

Emmanuel Charpentier

unread,
Jan 31, 2020, 2:58:10 PM1/31/20
to sage-release
Damn !

After make distclean and ./configure --without-system-libffi, make fails with the same error as before.

AND LIBFFI ISN'T COMPILED (no libffi* in logs/pkgs).

Relevant logs attached.
logs.tar.gz

Dima Pasechnik

unread,
Jan 31, 2020, 3:50:55 PM1/31/20
to sage-release
Please send SAGE_ROOT/config.log

this is the most interesting one, to understand why libffi didn't get built

On Fri, Jan 31, 2020 at 7:58 PM Emmanuel Charpentier
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/f168a0e4-3ad6-43d0-ada6-58b0744f3768%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 3:58:00 PM1/31/20
to sage-release


Le vendredi 31 janvier 2020 21:50:55 UTC+1, Dima Pasechnik a écrit :
Please send SAGE_ROOT/config.log

Attached.
 
config.log

Dima Pasechnik

unread,
Jan 31, 2020, 4:14:59 PM1/31/20
to sage-release
On Fri, Jan 31, 2020 at 8:58 PM Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
>
>
>
> Le vendredi 31 janvier 2020 21:50:55 UTC+1, Dima Pasechnik a écrit :
>>
>> Please send SAGE_ROOT/config.log

this looks good, and in fact libffi gets built; indeed, your install.log says:

[libffi-3.2.1] Copying package files from temporary location
/usr/local/sage-9/local/var/tmp/sage/build/libffi-3.2.1/inst to
/usr/local/sage-9/local
[libffi-3.2.1] Successfully installed libffi-3.2.1
[libffi-3.2.1] Deleting temporary build directory
[libffi-3.2.1] /usr/local/sage-9/local/var/tmp/sage/build/libffi-3.2.1
[libffi-3.2.1] Finished installing libffi-3.2.1.spkg

You might want to check for presense of libffi.so in local/lib/
but I'm positive it's there, so it's ECL build that's failing for
unrelated reasons, probably cause your headers are a bit broken
somewhere:
I guess ECL tries to use system headers, even though it should not.

My conjecture is that it was always the case, and it went unnoticed
until libffi 3.3 was released, with something broken.
Previously, even if libffi-dev (Debian) was installed, its headers
were similar enough to the one supplied by Sage to work,
so if they were picked up then it still worked.

To test this you might try to "apt remove libffi-dev" and then "./sage
-i ecl"; if I'm right here then it will work.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/f5b1c484-fd07-4abe-afc3-8afbd1468f75%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 4:33:14 PM1/31/20
to sage-release


Le vendredi 31 janvier 2020 22:14:59 UTC+1, Dima Pasechnik a écrit :
On Fri, Jan 31, 2020 at 8:58 PM Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
>
>
>
> Le vendredi 31 janvier 2020 21:50:55 UTC+1, Dima Pasechnik a écrit :
>>
>> Please send SAGE_ROOT/config.log

this looks good, and in fact libffi gets built; indeed, your install.log says:

[libffi-3.2.1] Copying package files from temporary location
/usr/local/sage-9/local/var/tmp/sage/build/libffi-3.2.1/inst to
/usr/local/sage-9/local
[libffi-3.2.1] Successfully installed libffi-3.2.1
[libffi-3.2.1] Deleting temporary build directory
[libffi-3.2.1] /usr/local/sage-9/local/var/tmp/sage/build/libffi-3.2.1
[libffi-3.2.1] Finished installing libffi-3.2.1.spkg

You might want to check for presense of libffi.so in local/lib/
but I'm positive it's there,

You're right. So why didn't I get the compilation log ?
 
so it's ECL build that's failing for
unrelated reasons, probably cause your  headers are a bit broken
somewhere:
I guess ECL tries to use system headers, even though it should not.

My conjecture is that it was always the case, and it went unnoticed
until libffi 3.3 was released, with something broken.
Previously, even if libffi-dev (Debian) was installed, its headers
were similar enough to the one supplied by Sage to work,
so if they were picked up then it still worked.

To test this you might try to "apt remove libffi-dev" and then "./sage
-i ecl"; if I'm right here then it will work.

I can do that but as a very temporary measure: removing libffi-dev break other parts of my system :

charpent@zen-book-flip:/usr/local/sage-9$ sudo apt-get remove -s libffi-dev
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
  gir1.2-poppler-0.18 libblkid-dev libbsd-dev libcairo-script-interpreter2
  libglib2.0-dev-bin libmount-dev libpixman-1-dev libselinux1-dev
  libsepol1-dev libxcb-render0-dev libxcb-shm0-dev
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
  ghc libcairo2-dev libffi-dev libglib2.0-dev libpoppler-glib-dev
0 mis à jour, 0 nouvellement installés, 5 à enlever et 0 non mis à jour.
Remv ghc [8.8.1+dfsg1+is+8.6.5+dfsg1-2+b1]
Remv libpoppler-glib-dev [0.71.0-6]
Remv libcairo2-dev [1.16.0-4]
Remv libglib2.0-dev [2.62.4-1+b1]
Remv libffi-dev [3.3-3]

I suippose I have to do the whole cycle (distclean ; configure ; make) again... Stay tuned.
 

Dima Pasechnik

unread,
Jan 31, 2020, 4:57:04 PM1/31/20
to sage-release
In fact, ./configure of ECL has an option --with-libffi-prefix=path
so most probably all we need to do is to point it at the right place.
Try

ECL_CONFIGURE=`pwd`/local ./sage -i ecl



On Fri, Jan 31, 2020 at 9:33 PM Emmanuel Charpentier
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/71899b52-1852-46be-9a1b-4ba00bf7c75b%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 5:20:00 PM1/31/20
to sage-release
I saw your answer too late : I already started the cycle.

It looks that removing libffi-dev worked: the cycle isn't yet finished, but my $SAGE_ROOT/local/bin now sports an ecl and an ecl-config binaries...

Any suggestion before I restore libffi-dev (and the packets that depended on it) ?

Dima Pasechnik

unread,
Jan 31, 2020, 5:47:50 PM1/31/20
to sage-release
On Fri, Jan 31, 2020 at 10:20 PM Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
>
> I saw your answer too late : I already started the cycle.
>
> It looks that removing libffi-dev worked: the cycle isn't yet finished, but my $SAGE_ROOT/local/bin now sports an ecl and an ecl-config binaries...
>
> Any suggestion before I restore libffi-dev (and the packets that depended on it) ?

No, I think we know what's going on.
I've opened https://trac.sagemath.org/ticket/29128 to deal with the problem.
Should not be hard if
ECL_CONFIGURE="--with-libffi-prefix=`pwd`/local" ./sage -i ecl
works after you get the system libffi headers reinstalled.


>
> Le vendredi 31 janvier 2020 22:57:04 UTC+1, Dima Pasechnik a écrit :
>>
>> In fact, ./configure of ECL has an option --with-libffi-prefix=path
>> so most probably all we need to do is to point it at the right place.
>> Try
>>
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/ae274f58-edb7-449a-adb5-2a7023cd859a%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 31, 2020, 6:41:33 PM1/31/20
to sage-release
No such luck. After reinstalling libffi-dev:

  • ECL_CONFIGURE="--with-libffi-prefix=`pwd`/local"  ./sage -i ecl  does nothing (cyles through the configuration twice)
  • ECL_CONFIGURE="--with-libffi-prefix=`pwd`/local"  ./sage -f ecl FAILS, with an error similar to previous attempts:

[ecl-16.1.2.p5] gcc -DECLDIR="\"/usr/local/sage-9/local/lib/ecl-16.1.2\"" -I. -I/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build -I/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/src/c -I../ecl/gc -DECL_API -DECL_NO_LEGACY    -I/usr/local/sage-9/local/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o sse2.o sse2.o.c
[ecl-16.1.2.p5] /usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/src/c/ffi.d:148:34: error: 'FFI_SYSV' undeclared here (not in a function)
[ecl-16.1.2.p5]   148 |         {@':cdecl', FFI_SYSV},
[ecl-16.1.2.p5]       |                                  ^       
[ecl-16.1.2.p5] make[4]: *** [Makefile:86: ffi.o] Error 1
[ecl-16.1.2.p5] make[4]: *** Waiting for unfinished jobs....
[ecl-16.1.2.p5] make[4]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build/c'
[ecl-16.1.2.p5] make[3]: *** [Makefile:119: libeclmin.a] Error 2
[ecl-16.1.2.p5] make[3]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build'
[ecl-16.1.2.p5] make[2]: *** [Makefile:70: all] Error 2
[ecl-16.1.2.p5] make[2]: Leaving directory '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5/src'
[ecl-16.1.2.p5] ********************************************************************************
[ecl-16.1.2.p5] Error building ecl-16.1.2.p5
[ecl-16.1.2.p5] ********************************************************************************
[ecl-16.1.2.p5] 
[ecl-16.1.2.p5] real 0m15.619s
[ecl-16.1.2.p5] user 0m50.255s
[ecl-16.1.2.p5] sys 0m6.262s
[ecl-16.1.2.p5] ************************************************************************
[ecl-16.1.2.p5] Error installing package ecl-16.1.2.p5
[ecl-16.1.2.p5] ************************************************************************
[ecl-16.1.2.p5] Please email sage-devel (http://groups.google.com/group/sage-devel)
[ecl-16.1.2.p5] explaining the problem and including the log file
[ecl-16.1.2.p5]   /usr/local/sage-9/logs/pkgs/ecl-16.1.2.p5.log
[ecl-16.1.2.p5] Describe your computer, operating system, etc.
[ecl-16.1.2.p5] If you want to try to fix the problem yourself, *don't* just cd to
[ecl-16.1.2.p5] /usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5 and type 'make' or whatever is appropriate.
[ecl-16.1.2.p5] Instead, the following commands setup all environment variables
[ecl-16.1.2.p5] correctly and load a subshell for you to debug the error:
[ecl-16.1.2.p5]   (cd '/usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5' && '/usr/local/sage-9/sage' --sh)
[ecl-16.1.2.p5] When you are done debugging, you can type "exit" to leave the subshell.
[ecl-16.1.2.p5] ************************************************************************
make[1]: *** [Makefile:2179: /usr/local/sage-9/local/var/lib/sage/installed/ecl-16.1.2.p5] Error 1
make[1] : on quitte le répertoire « /usr/local/sage-9/build/make »

real 0m17,320s
user 0m51,822s
sys 0m6,526s
***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make ecl'):

* package:         ecl-16.1.2.p5
  last build time: févr. 1 00:30
  log file:        /usr/local/sage-9/logs/pkgs/ecl-16.1.2.p5.log
  build directory: /usr/local/sage-9/local/var/tmp/sage/build/ecl-16.1.2.p5

I'm leaving this for tonight (re-switching to my many-times upgraded tree). Let me know if you need further tests.

Sébastien Labbé

unread,
Feb 1, 2020, 9:34:51 AM2/1/20
to sage-release
With Ubuntu 16.04, testing few optional and external packages, I get:

Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_numerical_backends_cplex,sage_numerical_backends_gurobi,sagenb

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Killed due to abort
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/misc/latex.py  # 1 doctest failed
sage -t --long src/sage/plot/animate.py  # 7 doctests failed
sage -t --long src/sage/sat/boolean_polynomials.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc


Rerunning failed tests, I get:

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Killed due to abort
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/misc/latex.py  # 1 doctest failed
sage -t --long src/sage/plot/animate.py  # 7 doctests failed
----------------------------------------------------------------------
External software detected for doctesting: ffmpeg,imagemagick,internet,latex

These issues are not new and already tracked at https://trac.sagemath.org/ticket/25536

The boolean_polynomials.py failed test which disappears is copied below.


sage -t --long src/sage/sat/boolean_polynomials.py
**********************************************************************
File "src/sage/sat/boolean_polynomials.py", line 89, in sage.sat.boolean_polynomials.solve
Failed example:
    s = solve_sat(F, s_verbosity=1, c_max_vars_sparse=4, c_cutting_number=8) # optional - cryptominisat
Expected:
    c ...
    ...
Got:
    <BLANKLINE>
**********************************************************************
1 item had failures:
   1 of  41 in sage.sat.boolean_polynomials.solve
    0 tests not run because we ran out of time
    [46 tests, 1 failure, 221.70 s]

Reply all
Reply to author
Forward
0 new messages