On Tue, 1 Oct 2019 at 13:42, Dima Pasechnik <dimp...@gmail.com> wrote:

> On Tue, Oct 1, 2019 at 7:43 PM John Cremona <john.crem...@gmail.com>
> wrote:
> >
> >
> >
> > On Tue, 1 Oct 2019 at 12:08, Dima Pasechnik <dimp...@gmail.com> wrote:
> >>
> >> On Tue, Oct 1, 2019 at 6:59 PM Dima Pasechnik <dimp...@gmail.com>
> wrote:
> >> >
> >> > It seems that these machines don't have readline development files
> >> > properly installed.
> >> >
> >> > Could you attach config.log ?
> >> >
> >> I mean the "main" config.log, not the ones from package builds.
> >
> >
> > Here it is.  I looks as if some version of readline was downloaded and
> installed.
> no, it says that Sage's readline will be built, because according to the
> test,
> there is no ncurses (or tinfo) installed.
>
> So I am puzzled that you say that the machine has libreadline-dev
> installed.
> Could you post the contents of this package?
>

$ apt show libreadline-dev
Package: libreadline-dev
Version: 6.3-8ubuntu2
Priority: optional
Section: libdevel
Source: readline6
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Original-Maintainer: Matthias Klose <d...@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 6,144 B
Depends: libreadline6-dev (= 6.3-8ubuntu2)
Conflicts: libreadline-gplv2-dev
Supported: 9m
Download-Size: 992 B
APT-Manual-Installed: yes
APT-Sources: http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: GNU readline and history libraries, development files
 The GNU readline library aids in the consistency of user interface
 across discrete programs that need to provide a command line
 interface.
 .
 The GNU history library provides a consistent user interface for
 recalling lines of previously typed input.
 .
 This package is a dependency package depending on libreadline6-dev.


> As well, I'd like to look at the output of
>
> $ ldd `find /usr -name libreadline.so`
>
> - which should look more or less like:
>
> linux-vdso.so.1 (0x00007ffc2a2ce000)
> libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x000079942a162000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000799429fa1000)
> /lib64/ld-linux-x86-64.so.2 (0x000079942a3f3000)
>

It finds the system one as well as two sage installation ones.  The system
one is like what you expected:

/usr/local/sage/sage-8.8/local/lib/libreadline.so:
        linux-vdso.so.1 =>  (0x00007ffd459fe000)
        libtinfo.so.6 => /usr/local/sage/sage-8.8/local/lib/libtinfo.so.6
(0x00007f9940e43000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9940a73000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f99412d3000)
/usr/local/sage/sage-8.9/local/lib/libreadline.so:
        linux-vdso.so.1 =>  (0x00007ffe9e4ce000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f00db8e3000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f00dbf03000)
/usr/lib/x86_64-linux-gnu/libreadline.so:
        linux-vdso.so.1 =>  (0x00007ffebbdd6000)
        libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5
(0x00007f2e72d1b000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2e7294b000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f2e73193000)


>
> I gather that the test we have for system's ncurses is too
> restrictive, and doesn't work
> even though it should... (So this is a potential Sage bug)
>
> To continue with this problem:
> Indeed, readline gets built by Sage, but it's a bit broken, as I
> gather it's not linked
> against libtinfo:
>
> To check this, please post the output of
>
>
$ ldd /usr/local/sage/sage-8.9/local/lib/libreadline.so.6
        linux-vdso.so.1 =>  (0x00007ffce3bbe000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbee541b000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fbee5a3b000)



>
> I don't know why this doesn't work, it might be something went wrong in
> ------------------
> commit 584735d9abe44b079df2566f7f73b6a69aaea0cf
> Author: Dima Pasechnik <dimp...@gmail.com>
> Date:   Wed May 1 10:58:00 2019 +0100
>
>     get termcap library name from the readline's configure
> --------------------
>
> (so this might be another Sage bug)
>
> ----------------------------------------------------
> Fixing at least one of these bugs might cure the systems you have, but
> more info is needed...
> What OS is that, precisely?
>

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.6 LTS
Release:        16.04
Codename:       xenial

(Same for all 6 machines.  I have tried to be consistent by reporting
answers to your questions all from the same one.)


>
> Sorry for trouble,
>

Not at all, thanks for your help.

On a more positive note, my python3 build on one of these machines was fine
after git pull trac develop.



> Dima
>
>
> And Python2 does not do a very good job gathering what extra libs are
> needed,
>  as its confugure output says
>
> checking how to link readline libs... -lreadline -ltermcap
>
> but then the error happens in the linking where one does not see
> -ltermcap, but
> rather -lcursesw
>
> (so this might be a Python2 bug)
>
>
>
> >
> > I can of course install more ubuntu packages on these machines (though I
> do have libreadline-dev installed already) but that's not quite the point
> here.
> >
> > John
> >
> >>
> >> >
> >> > On Tue, Oct 1, 2019 at 6:38 PM John Cremona <john.crem...@gmail.com>
> wrote:
> >> > >
> >> > > For a change instead of updating the git repository to build 8.9 I
> downloaded the file 8.9.tar.gz from the Releases section on github.  After
> unpacking and "make configure" I then did "make".  On 6 different machines,
> all running ubuntu, all the builds failed with
> >> > >
> >> > > Error building Sage.
> >> > >
> >> > > The following package(s) may have failed to build (not necessarily
> >> > > during this run of 'make all-start'):
> >> > >
> >> > > * package: python2-2.7.15.p1
> >> > >   log file: /usr/local/sage/sage-8.9/logs/pkgs/python2-2.7.15.p1.log
> >> > >   build directory:
> /usr/local/sage/sage-8.9/local/var/tmp/sage/build/python2-2.7.15.p1
> >> > >
> >> > > One logfile is attached, they all fail the same easy: something
> about readline.
> >> > >
> >> > > The point here is not so much what I should do to get around this,
> but rather, what is wrong with "make configure; make" which led it to
> happen on machines where the prerequisites for Sage are certainly all
> installed since they all have working versions of 8.8 (and many previous,
> and in some cases 8.9 prereleases) built from the github repo.
> >> > >
> >> > > John
> >> > >
> >> > > On Tue, 1 Oct 2019 at 09:07, Samuel Lelièvre <
> samuel.lelie...@gmail.com> wrote:
> >> > >>
> >> > >> ## Debian
> >> > >>
> >> > >> On Debian GNU/Linux 10 (buster), upgraded from
> >> > >> SageMath 8.9.rc0 via git and tested SageMath 8.9,
> >> > >> both py2 and py3. In both cases:
> >> > >> - `make`: ok
> >> > >> - `make testlong`: all tests pass!
> >> > >>
> >> > >> ## Cygwin
> >> > >>
> >> > >> On Cygwin64, tested SageMath 8.9, both py2 and py3,
> >> > >> with the following hardware and operating system:
> >> > >>
> >> > >> - laptop: HP ProBook 640 G1
> >> > >> - processor: Intel Core i7-4610M, 3.00 GHz
> >> > >> - memory: 8 GB
> >> > >> - Cygwin64 version: CYGWIN_NT-6.1 3.0.7 (0.338/5/3)
> >> > >> - Windows: Windows 7 Professional (64-bit), Service Pack 1
> >> > >>
> >> > >> ### Summary
> >> > >>
> >> > >> Here is a summary following this structure:
> >> > >>   - [file]  # [failures or timeouts during make testlong]
> >> > >>     --> [result when tested individually]; [ticket references]
> >> > >>
> >> > >> - py2:
> >> > >>   - src/sage/doctest/forker.py  # 4 doctests failed
> >> > >>     --> passes when tested individually
> >> > >>   - src/sage/parallel/map_reduce.py  # Timed out after testing
> finished
> >> > >>     --> passes when tested individually; might be #27537
> >> > >>
> >> > >> - py3
> >> > >>   - src/sage/coding/linear_code.py  # Timed out
> >> > >>     --> passes when tested individually; might be #26119
> >> > >>   - src/sage/libs/eclib/interface.py  # 1 doctest failed
> >> > >>     --> still fails when tested individually; see #28472 (positive
> review)
> >> > >>   - src/sage/rings/finite_rings/finite_field_base.pyx  # 1 doctest
> failed
> >> > >>     --> passes when tested individually
> >> > >>   - src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1
> doctest failed
> >> > >>     --> still fails when tested individually; this is #28334
> >> > >>   - src/sage_setup/clean.py  # 1 doctest failed
> >> > >>     --> still fails when tested individually
> >> > >>
> >> > >> Read on for the details for each of py2 and py3.
> >> > >>
> >> > >> ### Python 2
> >> > >>
> >> > >> Upgraded from SageMath 8.9.rc0 via git.
> >> > >> Ran `make`: success. Ran `make testlong` and individually
> >> > >> retested files that failed or timed out, see below.
> >> > >>
> >> > >> $ make testlong
> >> > >> ...
> >> > >>
> ----------------------------------------------------------------------
> >> > >> sage -t --long --warn-long 87.2 src/sage/doctest/forker.py  # 4
> doctests failed
> >> > >> sage -t --long --warn-long 87.2 src/sage/parallel/map_reduce.py  #
> >> > >> Timed out after testing finished
> >> > >>
> ----------------------------------------------------------------------
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2 src/sage/doctest/forker.py
> >> > >> Running doctests with ID 2019-10-01-08-19-19-2f160fbc.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2 src/sage/doctest/forker.py
> >> > >>     [449 tests, 34.21 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> All tests passed!
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 81.7 seconds
> >> > >>     cpu time: 5.5 seconds
> >> > >>     cumulative wall time: 34.2 seconds
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2 src/sage/parallel/map_reduce.py
> >> > >> Running doctests with ID 2019-10-01-08-21-35-400c0707.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2 src/sage/parallel/map_reduce.py
> >> > >>     [294 tests, 33.43 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> All tests passed!
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 34.0 seconds
> >> > >>     cpu time: 5.2 seconds
> >> > >>     cumulative wall time: 33.4 seconds
> >> > >>
> >> > >> ### Python 3
> >> > >>
> >> > >> Upgraded from SageMath 8.9.rc0 via git.
> >> > >> Ran `make`: success. Ran `make testlong` and individually
> >> > >> retested files that failed or timed out, see below.
> >> > >>
> >> > >> $ make testlong
> >> > >> ...
> >> > >>
> ----------------------------------------------------------------------
> >> > >> sage -t --long --warn-long 87.2 src/sage/coding/linear_code.py  #
> Timed out
> >> > >> sage -t --long --warn-long 87.2 src/sage/libs/eclib/interface.py
> # 1
> >> > >> doctest failed
> >> > >> sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/finite_rings/finite_field_base.pyx  # 1 doctest
> failed
> >> > >> sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1
> doctest
> >> > >> failed
> >> > >> sage -t --long --warn-long 87.2 src/sage_setup/clean.py  # 1
> doctest failed
> >> > >>
> ----------------------------------------------------------------------
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2 src/sage/coding/linear_code.py
> >> > >> Running doctests with ID 2019-10-01-07-58-10-19e3fc53.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2 src/sage/coding/linear_code.py
> >> > >>     [749 tests, 28.33 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> All tests passed!
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 29.2 seconds
> >> > >>     cpu time: 25.8 seconds
> >> > >>     cumulative wall time: 28.3 seconds
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2
> src/sage/libs/eclib/interface.py
> >> > >> Running doctests with ID 2019-10-01-07-58-59-bd646d17.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2 src/sage/libs/eclib/interface.py
> >> > >>
> **********************************************************************
> >> > >> File "src/sage/libs/eclib/interface.py", line 597, in
> >> > >> sage.libs.eclib.interface.mwrank_EllipticCurve.saturate
> >> > >> Failed example:
> >> > >>     E.saturation([Q1,Q2])
> >> > >> Expected:
> >> > >>     ([(1 : -27 : 1), (157 : 1950 : 1)], 3, 0.801588644684981)
> >> > >> Got:
> >> > >>     Attempt to round -0.2617840677e25 to a long int fails,
> aborting!
> >> > >>     ([(1 : -27 : 1), (157 : 1950 : 1)], 3, 0.801588644684981)
> >> > >>
> **********************************************************************
> >> > >> 1 item had failures:
> >> > >>    1 of   9 in
> sage.libs.eclib.interface.mwrank_EllipticCurve.saturate
> >> > >>     [192 tests, 1 failure, 5.96 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> sage -t --long --warn-long 87.2 src/sage/libs/eclib/interface.py
> # 1
> >> > >> doctest failed
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 6.5 seconds
> >> > >>     cpu time: 5.7 seconds
> >> > >>     cumulative wall time: 6.0 seconds
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/finite_rings/finite_field_base.pyx
> >> > >> Running doctests with ID 2019-10-01-08-01-55-2dd8733a.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/finite_rings/finite_field_base.pyx
> >> > >>     [272 tests, 18.14 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> All tests passed!
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 18.7 seconds
> >> > >>     cpu time: 18.0 seconds
> >> > >>     cumulative wall time: 18.1 seconds
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/polynomial/polynomial_rational_flint.pyx
> >> > >> Running doctests with ID 2019-10-01-08-03-34-441e450a.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/polynomial/polynomial_rational_flint.pyx
> >> > >>
> **********************************************************************
> >> > >> File "src/sage/rings/polynomial/polynomial_rational_flint.pyx",
> line
> >> > >> 2055, in
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
> >> > >> Failed example:
> >> > >>     G = f.galois_group(); G
> >> > >> Expected:
> >> > >>     Transitive group number 5 of degree 4
> >> > >> Got:
> >> > >>     Exception (FLINT memory_manager). Unable to allocate memory.
> >> > >>     Transitive group number 5 of degree 4
> >> > >>
> **********************************************************************
> >> > >> 1 item had failures:
> >> > >>    1 of  16 in
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
> >> > >>     [397 tests, 1 failure, 5.79 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> sage -t --long --warn-long 87.2
> >> > >> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1
> doctest
> >> > >> failed
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 6.3 seconds
> >> > >>     cpu time: 4.7 seconds
> >> > >>     cumulative wall time: 5.8 seconds
> >> > >>
> >> > >> $ ./sage -t --long --warn-long 87.2 src/sage_setup/clean.py
> >> > >> Running doctests with ID 2019-10-01-08-04-44-25198bd4.
> >> > >> Git branch: develop
> >> > >> Using --optional=build,dochtml,python2,sage
> >> > >> Doctesting 1 file.
> >> > >> sage -t --long --warn-long 87.2 src/sage_setup/clean.py
> >> > >>
> **********************************************************************
> >> > >> File "src/sage_setup/clean.py", line 100, in
> sage_setup.clean._find_stale_files
> >> > >> Failed example:
> >> > >>     for f in stale_iter:
> >> > >>         if f.endswith(skip_extensions): continue
> >> > >>         print('Found stale file: ' + f)
> >> > >> Expected nothing
> >> > >> Got:
> >> > >>     Found stale file:
> sage/graphs/__pycache__/line_graph.cpython-37.pyc
> >> > >>
> **********************************************************************
> >> > >> 1 item had failures:
> >> > >>    1 of  11 in sage_setup.clean._find_stale_files
> >> > >>     [17 tests, 1 failure, 0.51 s]
> >> > >>
> ----------------------------------------------------------------------
> >> > >> sage -t --long --warn-long 87.2 src/sage_setup/clean.py  # 1
> doctest failed
> >> > >>
> ----------------------------------------------------------------------
> >> > >> Total time for all tests: 1.0 seconds
> >> > >>     cpu time: 0.5 seconds
> >> > >>     cumulative wall time: 0.5 seconds
> >> > >>
> >> > >> --
> >> > >> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/CAEcArF06vXMyROkEshs%3DYV1_500kbwPDhQGJBH39B14i8Ku3Qg%40mail.gmail.com
> .
> >> > >
> >> > > --
> >> > > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/CAD0p0K7hW%3DTd2LqSa%2BybC-DrPgymFr8cvSHPRpEKnNwoMq%2Bpwg%40mail.gmail.com
> .
> >>
> >> --
> >> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/CAAWYfq1x7jY7f%3DeJ2u%2BdYuTE27H_3P%2B_9jRZtBGu8%2BaJv%3DUYRA%40mail.gmail.com
> .
> >
> > --
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/CAD0p0K6FUy-q%3DZurAgHbi3j6vvwQwqhXOiYYQhntXv92wkEgJA%40mail.gmail.com
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/CAAWYfq2X7zP4AKCkKrRtJObAwHKPO_-CDhApX5j6vD4pmk-f8g%40mail.gmail.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAD0p0K63ZXneidvbAbm%3DQG3Yu9xHfdPmm41nCXExnA2FTxZfdw%40mail.gmail.com.

Reply via email to