[sage-release] Re: Sage 9.1.beta0 released
I was late on this one, but let me post it for comparison purposes. 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/databases/oeis.py # 1 doctest 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/repl/load.py # 1 doctest failed sage -t --long src/sage/symbolic/integration/external.py # 1 doctest failed -- External software detected for doctesting: cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc Rerunning failed tests gives: -- sage -t --long src/sage/databases/findstat.py # 8 doctests failed sage -t --long src/sage/databases/oeis.py # 1 doctest 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/repl/load.py # 1 doctest failed -- External software detected for doctesting: ffmpeg,imagemagick,internet,latex Follow up at: https://trac.sagemath.org/ticket/25536 -- 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/b61d629a-c0c2-40d6-94dc-fc98076e583b%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
On a slightly smaller machine (Debian testing, core i5, 8 GB RAM) with different installed software, an upgrade of 9.0 to 9.1.beta0 (Python 3-based) leads to ptestalllong getting 12 failures, all transient: Using –optional=build,dochtml,dot2tex,external,fricas,giacpy_sage,libsemigroups,memlimit,python2,sage,sagenb External software to be detected: cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,macaulay2,magma,maple,mathematica,matlab,octave,pandoc,scilab File Result P/T src/sage/plot/animate.py 7 doctests failed T src/sage/combinat/designs/ext_rep.py 2 doctests failed T src/sage/symbolic/integration/external.py 1 doctest failed T src/doc/en/constructions/linear_algebra.rst 1 doctest failed T src/sage/misc/latex.py 1 doctest failed T src/doc/en/constructions/interface_issues.rst 1 doctest failed T src/sage/databases/oeis.py 1 doctest failed T src/sage/repl/load.py 1 doctest failed T src/doc/en/developer/coding_in_other.rst 1 doctest failed T src/sage/interfaces/octave.py 3 doctests failed T src/sage/databases/findstat.py 8 doctests failed T src/sage/interfaces/magma_free.py 2 doctests failed T External software detected for doctesting: ffmpeg,graphviz,imagemagick,internet,latex,mathematica,octave,pandoc HTH, Le samedi 11 janvier 2020 14:07:34 UTC+1, Emmanuel Charpentier a écrit : On Debian testing running on core i7 + 16 GB RAM, upgrading a Python > 3-based Sage 9.0 to 9.1.beta0 and running ptestalllong gets 3 permanent > and 5 transient failures: > File Result P/T > src/sage/databases/oeis.py 1 doctest failed T > src/sage/plot/animate.py 7 doctests failed T > src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P > src/sage/tests/gap_packages.py 1 doctest failed P > src/sage/misc/latex.py 1 doctest failed T > src/sage/libs/glpk/error.pyx 1 doctest failed P > src/sage/repl/load.py 1 doctest failed T > src/sage/databases/findstat.py 8 doctests failed T > > All of these failures have been reported multiple times. No new failure > here. > > HTH, > > Le vendredi 10 janvier 2020 17:19:30 UTC+1, Volker Braun a écrit : > > 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 >> >> >> b8f53f72e8 (HEAD -> develop, tag: 9.1.beta0, trac/develop) Updated >> SageMath version to 9.1.beta0 >> 7140d0e7bb Trac #28389: Support constructing Singular ring with ring >> order with 'c' or 'C' >> 1f04f40d45 Trac #27513: Allow custom order for edges as well as vertices >> for incidence matrix >> 5c3676468a Trac #28950: more precise assert statements >> 56ef6f028c Trac #28948: some preparation for ipython7 >> d6b83409eb Trac #28947: multiplicative Abelian groups are not GAP friendly >> 5762334c54 Trac #28938: remove deprecated methods in some combinatorial >> Hopf algebras >> ae18b5d03e Trac #28937: change some doc about python3 >> ba2f949961 Trac #28935: infinite recursion in exponential of sparse >> matrices >> b731e8b1af Trac #28933: no longer use _cmp_ in vectors >> 51e7813414 Trac #28929: HyperbolicGeodesic.plot() returns None if self is >> a line and boundary=False >> 2b596aad84 Trac #28927: DESTDIR support for libbraiding and libhomfly >> 6bfc8ed6d0 Trac #28909: Allow overriding "when building, check that user >> isn't root" for use in Docker containers with configure >> --enable-build-as-root >> f5c516cb00 Trac #28884: spkg-configure for R >> c4ed371cdf Trac #28879: spkg-configure for GSL >> 3047e9e8c3 Trac #28855: PolynomialRing random_element()s aren't always >> ring elements >> da593dc5f5 Trac #28688: fix buckygen for modern C/C++ >> 896120d9fd Trac #27870: spkg-configure.m4 for $(BLAS) (i.e. atlas and >> openblas) >> 304fe834c5 Trac #25903: fix Macaulay2 output when reading input from a >> file >> 1e5c93fadf Trac #7165: sage fails to plot a quarter circle when it should >> e9db0c6dde Trac #28903: Sympy-conversion of complex numbers >> 2111e0063b Trac #28899: some details in rings/polynomial/ >> f8c7d3650d Trac #28848: Add methods for the lattice of subsets >> 2ec94231bf Trac #28557: julia_plot sometimes does not draw the entire >> julia set >> c80928120c Trac #23946: Exhaust over Weil polynomials >> c767179b74 Trac #28930: pyflakes fix in dynamics >> 1a8f1fa3fa Trac #28926: MR39: Update Developer's guide regarding pull >> requests >> 16052a5aa6 Trac #28919: spkg-configure for tachyon >> 1890aefa44 Trac #28914: default_mip_solver: Allow solver = a callable >> ebb0d39a81 Trac #28911: Update sympy to 1.5 >> 889d29cb9b Trac #28897: BipartiteGraph blindly trusts generic graphs >> 082db1579a Trac #28889: HyperbolicGeodesic.angle() returns mathematically >> incorrect results >> 3914a955ab Trac #28883: update pkgconfig to version 1.5.1 >> e8987e793c Trac #28646: Use CombinatorialPolyhedron to obtain faces of >> polyhedra >> 4fc6fba1e8 Trac #28311: Random failure in >> combinatorial_polyhedron/base.pyx >> 5fa32aa9f8 Trac #28175:
Re: [sage-release] Re: Sage 9.1.beta0 released
probably you need to rebuild at least sagelib. ./sage -f sagelib On Wed, Jan 15, 2020 at 1:18 PM 'Martin R' via sage-release wrote: > > For the record: > > ImportError: /usr/lib/x86_64-linux-gnu/libgsl.so.23: undefined symbol: > cblas_ctrmv > > > Am Mittwoch, 15. Januar 2020 14:16:39 UTC+1 schrieb Martin R: >> >> I'm afraid I was celebrating too early. make build succeeded, but sage >> doesn't start anymore now. I guess I should start from scratch. :-( >> >> Am Mittwoch, 15. Januar 2020 14:07:49 UTC+1 schrieb Martin R: >>> >>> BINGO!!! >>> >>> Many many many thanks! >>> >>> Martin >>> >>> Am Mittwoch, 15. Januar 2020 14:00:29 UTC+1 schrieb Dima Pasechnik: Note that you need to uninstall bzip2, xz, pcre, readline, curl before the corresponding system versions are picked up by ./configure (of course all this is not needed for fresh builds...) if this does not help please post config.log On Wed, Jan 15, 2020 at 12:53 PM 'Martin R' via sage-release wrote: > > > > Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release >> wrote: >> > >> > Oh dea, this is becoming strange: >> > >> > The output of configure says that >> > >> > atlas, openblas, iconv will NOT be installed, but >> > >> > bzip2-1.0.6-20150304.p0 >> > readline-6.3.008.p0 >> > xz-5.2.2.p0 >> > pcre-8.40.p2 >> > curl-7.62.0.p0 >> > >> > However, I certainly have bzip2, xz, pcre and curl on my system, and >> > I guess also readline. >> > >> > Might there be a bug in configure? >> >> You need development versions of these, see >> https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation >> >> So, on Ubuntu: >> >> libbz2-dev >> libreadline-dev (seems to be missing in docs) >> liblzma-dev (this is the xz lib, iirc) >> libpcre3-dev >> libcurl4-openssl-dev > > >> >> the last of these, libcurl4-openssl-dev was indeed missing, but >> configure still wants to build r :-( > > > Martin >> >> >> >> > >> > Martin >> > >> > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release >> >> wrote: >> >> > >> >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: >> >> >> >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >> >> >> wrote: >> >> >> > >> >> >> > Thanks again! It still tries to build R and fails >> >> >> > >> >> >> > I checked that system R starts, it does (R version 3.4.4) >> >> >> Please also make sure that >> >> >> >> >> >> pkg-config --modversion libR >> >> >> >> >> >> outputs the version. >> >> >> >> >> > Yes, it does. >> >> > >> >> >> >> >> >> However there is just no "checking for R" message in your >> >> >> config.log, >> >> >> it indicates that there are still remains of R left >> >> >> in your installation. >> >> >> >> >> >> I've opened https://trac.sagemath.org/ticket/29016 >> >> >> to deal with R being hard to clean away - feel free to try it. >> >> >> >> >> >> Maybe you also need to run >> >> >> >> >> >> make r-clean >> >> > >> >> > >> >> > I did that, it says that there is no legacy uninstaller for r, and >> >> > that there is nothing to do. I checked for the files in the >> >> > ticket, but none of them exists. :-( >> >> > >> >> > The config.log contains the lines >> >> > >> >> > configure:18950: checking installing any of atlas openblas iconv >> >> > readline bzip2 xz pcre curl? >> >> > configure:18954: result: yes; install r as well >> >> > >> >> > but I do not know how to find out which of those (atlas openblas >> >> > iconv readline bzip2 xz pcre curl) is the problem. >> >> >> >> The easiest is to look at the output of ./configure >> >> It should contain lines like >> >> >> >> atlas-3.10.2.p3 will not be installed (configure check) >> >> >> >> for each of the packages in that list. >> >> So for any of these that are not marked this way, please install the >> >> corresponding system package >> >> and re-run configure. >> >> >> >> >> >> >> >> > >> >> > Martin >> >> > >> >> > -- >> >> > 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-r...@googlegroups.com. >> >> > To view this discussion on the web visit
Re: [sage-release] Re: Sage 9.1.beta0 released
For the record: ImportError: /usr/lib/x86_64-linux-gnu/libgsl.so.23: undefined symbol: cblas_ctrmv Am Mittwoch, 15. Januar 2020 14:16:39 UTC+1 schrieb Martin R: > > I'm afraid I was celebrating too early. make build succeeded, but sage > doesn't start anymore now. I guess I should start from scratch. :-( > > Am Mittwoch, 15. Januar 2020 14:07:49 UTC+1 schrieb Martin R: >> >> BINGO!!! >> >> Many many many thanks! >> >> Martin >> >> Am Mittwoch, 15. Januar 2020 14:00:29 UTC+1 schrieb Dima Pasechnik: >>> >>> Note that you need to uninstall bzip2, xz, pcre, readline, curl before >>> the corresponding system >>> versions are picked up by ./configure (of course all this is not >>> needed for fresh builds...) >>> >>> if this does not help please post config.log >>> >>> On Wed, Jan 15, 2020 at 12:53 PM 'Martin R' via sage-release >>> wrote: >>> > >>> > >>> > >>> > Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: >>> >> >>> >> On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release >>> >> wrote: >>> >> > >>> >> > Oh dea, this is becoming strange: >>> >> > >>> >> > The output of configure says that >>> >> > >>> >> > atlas, openblas, iconv will NOT be installed, but >>> >> > >>> >> > bzip2-1.0.6-20150304.p0 >>> >> > readline-6.3.008.p0 >>> >> > xz-5.2.2.p0 >>> >> > pcre-8.40.p2 >>> >> > curl-7.62.0.p0 >>> >> > >>> >> > However, I certainly have bzip2, xz, pcre and curl on my system, >>> and I guess also readline. >>> >> > >>> >> > Might there be a bug in configure? >>> >> >>> >> You need development versions of these, see >>> >> >>> https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation >>> >>> >> >>> >> So, on Ubuntu: >>> >> >>> >> libbz2-dev >>> >> libreadline-dev (seems to be missing in docs) >>> >> liblzma-dev (this is the xz lib, iirc) >>> >> libpcre3-dev >>> >> libcurl4-openssl-dev >>> > >>> > >>> >> >>> >> the last of these, libcurl4-openssl-dev was indeed missing, but >>> configure still wants to build r :-( >>> > >>> > >>> > Martin >>> >> >>> >> >>> >> >>> >> > >>> >> > Martin >>> >> > >>> >> > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: >>> >> >> >>> >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release >>> >> >> wrote: >>> >> >> > >>> >> >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima >>> Pasechnik: >>> >> >> >> >>> >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >>> >> >> >> wrote: >>> >> >> >> > >>> >> >> >> > Thanks again! It still tries to build R and fails >>> >> >> >> > >>> >> >> >> > I checked that system R starts, it does (R version 3.4.4) >>> >> >> >> Please also make sure that >>> >> >> >> >>> >> >> >> pkg-config --modversion libR >>> >> >> >> >>> >> >> >> outputs the version. >>> >> >> >> >>> >> >> > Yes, it does. >>> >> >> > >>> >> >> >> >>> >> >> >> However there is just no "checking for R" message in your >>> config.log, >>> >> >> >> it indicates that there are still remains of R left >>> >> >> >> in your installation. >>> >> >> >> >>> >> >> >> I've opened https://trac.sagemath.org/ticket/29016 >>> >> >> >> to deal with R being hard to clean away - feel free to try it. >>> >> >> >> >>> >> >> >> Maybe you also need to run >>> >> >> >> >>> >> >> >> make r-clean >>> >> >> > >>> >> >> > >>> >> >> > I did that, it says that there is no legacy uninstaller for r, >>> and that there is nothing to do. I checked for the files in the ticket, >>> but none of them exists. :-( >>> >> >> > >>> >> >> > The config.log contains the lines >>> >> >> > >>> >> >> > configure:18950: checking installing any of atlas openblas iconv >>> readline bzip2 xz pcre curl? >>> >> >> > configure:18954: result: yes; install r as well >>> >> >> > >>> >> >> > but I do not know how to find out which of those (atlas openblas >>> iconv readline bzip2 xz pcre curl) is the problem. >>> >> >> >>> >> >> The easiest is to look at the output of ./configure >>> >> >> It should contain lines like >>> >> >> >>> >> >> atlas-3.10.2.p3 will not be installed (configure check) >>> >> >> >>> >> >> for each of the packages in that list. >>> >> >> So for any of these that are not marked this way, please install >>> the >>> >> >> corresponding system package >>> >> >> and re-run configure. >>> >> >> >>> >> >> >>> >> >> >>> >> >> > >>> >> >> > Martin >>> >> >> > >>> >> >> > -- >>> >> >> > 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-r...@googlegroups.com. >>> >> >> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.com. >>> >>> >>> >> > >>> >> > -- >>> >> > You received this message because you are subscribed to the Google >>>
Re: [sage-release] Re: Sage 9.1.beta0 released
I'm afraid I was celebrating too early. make build succeeded, but sage doesn't start anymore now. I guess I should start from scratch. :-( Am Mittwoch, 15. Januar 2020 14:07:49 UTC+1 schrieb Martin R: > > BINGO!!! > > Many many many thanks! > > Martin > > Am Mittwoch, 15. Januar 2020 14:00:29 UTC+1 schrieb Dima Pasechnik: >> >> Note that you need to uninstall bzip2, xz, pcre, readline, curl before >> the corresponding system >> versions are picked up by ./configure (of course all this is not >> needed for fresh builds...) >> >> if this does not help please post config.log >> >> On Wed, Jan 15, 2020 at 12:53 PM 'Martin R' via sage-release >> wrote: >> > >> > >> > >> > Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release >> >> wrote: >> >> > >> >> > Oh dea, this is becoming strange: >> >> > >> >> > The output of configure says that >> >> > >> >> > atlas, openblas, iconv will NOT be installed, but >> >> > >> >> > bzip2-1.0.6-20150304.p0 >> >> > readline-6.3.008.p0 >> >> > xz-5.2.2.p0 >> >> > pcre-8.40.p2 >> >> > curl-7.62.0.p0 >> >> > >> >> > However, I certainly have bzip2, xz, pcre and curl on my system, and >> I guess also readline. >> >> > >> >> > Might there be a bug in configure? >> >> >> >> You need development versions of these, see >> >> >> https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation >> >> >> >> >> So, on Ubuntu: >> >> >> >> libbz2-dev >> >> libreadline-dev (seems to be missing in docs) >> >> liblzma-dev (this is the xz lib, iirc) >> >> libpcre3-dev >> >> libcurl4-openssl-dev >> > >> > >> >> >> >> the last of these, libcurl4-openssl-dev was indeed missing, but >> configure still wants to build r :-( >> > >> > >> > Martin >> >> >> >> >> >> >> >> > >> >> > Martin >> >> > >> >> > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: >> >> >> >> >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release >> >> >> wrote: >> >> >> > >> >> >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima >> Pasechnik: >> >> >> >> >> >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >> >> >> >> wrote: >> >> >> >> > >> >> >> >> > Thanks again! It still tries to build R and fails >> >> >> >> > >> >> >> >> > I checked that system R starts, it does (R version 3.4.4) >> >> >> >> Please also make sure that >> >> >> >> >> >> >> >> pkg-config --modversion libR >> >> >> >> >> >> >> >> outputs the version. >> >> >> >> >> >> >> > Yes, it does. >> >> >> > >> >> >> >> >> >> >> >> However there is just no "checking for R" message in your >> config.log, >> >> >> >> it indicates that there are still remains of R left >> >> >> >> in your installation. >> >> >> >> >> >> >> >> I've opened https://trac.sagemath.org/ticket/29016 >> >> >> >> to deal with R being hard to clean away - feel free to try it. >> >> >> >> >> >> >> >> Maybe you also need to run >> >> >> >> >> >> >> >> make r-clean >> >> >> > >> >> >> > >> >> >> > I did that, it says that there is no legacy uninstaller for r, >> and that there is nothing to do. I checked for the files in the ticket, >> but none of them exists. :-( >> >> >> > >> >> >> > The config.log contains the lines >> >> >> > >> >> >> > configure:18950: checking installing any of atlas openblas iconv >> readline bzip2 xz pcre curl? >> >> >> > configure:18954: result: yes; install r as well >> >> >> > >> >> >> > but I do not know how to find out which of those (atlas openblas >> iconv readline bzip2 xz pcre curl) is the problem. >> >> >> >> >> >> The easiest is to look at the output of ./configure >> >> >> It should contain lines like >> >> >> >> >> >> atlas-3.10.2.p3 will not be installed (configure check) >> >> >> >> >> >> for each of the packages in that list. >> >> >> So for any of these that are not marked this way, please install >> the >> >> >> corresponding system package >> >> >> and re-run configure. >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > Martin >> >> >> > >> >> >> > -- >> >> >> > 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-r...@googlegroups.com. >> >> >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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-r...@googlegroups.com. >> >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-release/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.com. >> >> >>
Re: [sage-release] Re: Sage 9.1.beta0 released
BINGO!!! Many many many thanks! Martin Am Mittwoch, 15. Januar 2020 14:00:29 UTC+1 schrieb Dima Pasechnik: > > Note that you need to uninstall bzip2, xz, pcre, readline, curl before > the corresponding system > versions are picked up by ./configure (of course all this is not > needed for fresh builds...) > > if this does not help please post config.log > > On Wed, Jan 15, 2020 at 12:53 PM 'Martin R' via sage-release > > wrote: > > > > > > > > Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: > >> > >> On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release > >> wrote: > >> > > >> > Oh dea, this is becoming strange: > >> > > >> > The output of configure says that > >> > > >> > atlas, openblas, iconv will NOT be installed, but > >> > > >> > bzip2-1.0.6-20150304.p0 > >> > readline-6.3.008.p0 > >> > xz-5.2.2.p0 > >> > pcre-8.40.p2 > >> > curl-7.62.0.p0 > >> > > >> > However, I certainly have bzip2, xz, pcre and curl on my system, and > I guess also readline. > >> > > >> > Might there be a bug in configure? > >> > >> You need development versions of these, see > >> > https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation > > >> > >> So, on Ubuntu: > >> > >> libbz2-dev > >> libreadline-dev (seems to be missing in docs) > >> liblzma-dev (this is the xz lib, iirc) > >> libpcre3-dev > >> libcurl4-openssl-dev > > > > > >> > >> the last of these, libcurl4-openssl-dev was indeed missing, but > configure still wants to build r :-( > > > > > > Martin > >> > >> > >> > >> > > >> > Martin > >> > > >> > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: > >> >> > >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release > >> >> wrote: > >> >> > > >> >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima > Pasechnik: > >> >> >> > >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release > >> >> >> wrote: > >> >> >> > > >> >> >> > Thanks again! It still tries to build R and fails > >> >> >> > > >> >> >> > I checked that system R starts, it does (R version 3.4.4) > >> >> >> Please also make sure that > >> >> >> > >> >> >> pkg-config --modversion libR > >> >> >> > >> >> >> outputs the version. > >> >> >> > >> >> > Yes, it does. > >> >> > > >> >> >> > >> >> >> However there is just no "checking for R" message in your > config.log, > >> >> >> it indicates that there are still remains of R left > >> >> >> in your installation. > >> >> >> > >> >> >> I've opened https://trac.sagemath.org/ticket/29016 > >> >> >> to deal with R being hard to clean away - feel free to try it. > >> >> >> > >> >> >> Maybe you also need to run > >> >> >> > >> >> >> make r-clean > >> >> > > >> >> > > >> >> > I did that, it says that there is no legacy uninstaller for r, and > that there is nothing to do. I checked for the files in the ticket, but > none of them exists. :-( > >> >> > > >> >> > The config.log contains the lines > >> >> > > >> >> > configure:18950: checking installing any of atlas openblas iconv > readline bzip2 xz pcre curl? > >> >> > configure:18954: result: yes; install r as well > >> >> > > >> >> > but I do not know how to find out which of those (atlas openblas > iconv readline bzip2 xz pcre curl) is the problem. > >> >> > >> >> The easiest is to look at the output of ./configure > >> >> It should contain lines like > >> >> > >> >> atlas-3.10.2.p3 will not be installed (configure check) > >> >> > >> >> for each of the packages in that list. > >> >> So for any of these that are not marked this way, please install the > >> >> corresponding system package > >> >> and re-run configure. > >> >> > >> >> > >> >> > >> >> > > >> >> > Martin > >> >> > > >> >> > -- > >> >> > 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-r...@googlegroups.com. > >> >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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-r...@googlegroups.com. > >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.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-r...@googlegroups.com . > > To view this discussion on the web visit >
Re: [sage-release] Re: Sage 9.1.beta0 released
Note that you need to uninstall bzip2, xz, pcre, readline, curl before the corresponding system versions are picked up by ./configure (of course all this is not needed for fresh builds...) if this does not help please post config.log On Wed, Jan 15, 2020 at 12:53 PM 'Martin R' via sage-release wrote: > > > > Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release >> wrote: >> > >> > Oh dea, this is becoming strange: >> > >> > The output of configure says that >> > >> > atlas, openblas, iconv will NOT be installed, but >> > >> > bzip2-1.0.6-20150304.p0 >> > readline-6.3.008.p0 >> > xz-5.2.2.p0 >> > pcre-8.40.p2 >> > curl-7.62.0.p0 >> > >> > However, I certainly have bzip2, xz, pcre and curl on my system, and I >> > guess also readline. >> > >> > Might there be a bug in configure? >> >> You need development versions of these, see >> https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation >> >> So, on Ubuntu: >> >> libbz2-dev >> libreadline-dev (seems to be missing in docs) >> liblzma-dev (this is the xz lib, iirc) >> libpcre3-dev >> libcurl4-openssl-dev > > >> >> the last of these, libcurl4-openssl-dev was indeed missing, but configure >> still wants to build r :-( > > > Martin >> >> >> >> > >> > Martin >> > >> > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release >> >> wrote: >> >> > >> >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: >> >> >> >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >> >> >> wrote: >> >> >> > >> >> >> > Thanks again! It still tries to build R and fails >> >> >> > >> >> >> > I checked that system R starts, it does (R version 3.4.4) >> >> >> Please also make sure that >> >> >> >> >> >> pkg-config --modversion libR >> >> >> >> >> >> outputs the version. >> >> >> >> >> > Yes, it does. >> >> > >> >> >> >> >> >> However there is just no "checking for R" message in your config.log, >> >> >> it indicates that there are still remains of R left >> >> >> in your installation. >> >> >> >> >> >> I've opened https://trac.sagemath.org/ticket/29016 >> >> >> to deal with R being hard to clean away - feel free to try it. >> >> >> >> >> >> Maybe you also need to run >> >> >> >> >> >> make r-clean >> >> > >> >> > >> >> > I did that, it says that there is no legacy uninstaller for r, and that >> >> > there is nothing to do. I checked for the files in the ticket, but >> >> > none of them exists. :-( >> >> > >> >> > The config.log contains the lines >> >> > >> >> > configure:18950: checking installing any of atlas openblas iconv >> >> > readline bzip2 xz pcre curl? >> >> > configure:18954: result: yes; install r as well >> >> > >> >> > but I do not know how to find out which of those (atlas openblas iconv >> >> > readline bzip2 xz pcre curl) is the problem. >> >> >> >> The easiest is to look at the output of ./configure >> >> It should contain lines like >> >> >> >> atlas-3.10.2.p3 will not be installed (configure check) >> >> >> >> for each of the packages in that list. >> >> So for any of these that are not marked this way, please install the >> >> corresponding system package >> >> and re-run configure. >> >> >> >> >> >> >> >> > >> >> > Martin >> >> > >> >> > -- >> >> > 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-r...@googlegroups.com. >> >> > To view this discussion on the web visit >> >> > https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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-r...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-release/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.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/a2512246-f441-4ace-82df-fd1f354bcaf5%40googlegroups.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/CAAWYfq2u6ZH1zEZGcpP%2BcjgCMoq9iZGjyPvf96g7kJAa7O_A0w%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
Am Mittwoch, 15. Januar 2020 13:23:17 UTC+1 schrieb Dima Pasechnik: > > On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release > > wrote: > > > > Oh dea, this is becoming strange: > > > > The output of configure says that > > > > atlas, openblas, iconv will NOT be installed, but > > > > bzip2-1.0.6-20150304.p0 > > readline-6.3.008.p0 > > xz-5.2.2.p0 > > pcre-8.40.p2 > > curl-7.62.0.p0 > > > > However, I certainly have bzip2, xz, pcre and curl on my system, and I > guess also readline. > > > > Might there be a bug in configure? > > You need development versions of these, see > > https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation > > > So, on Ubuntu: > > libbz2-dev > libreadline-dev (seems to be missing in docs) > liblzma-dev (this is the xz lib, iirc) > libpcre3-dev > libcurl4-openssl-dev > the last of these, libcurl4-openssl-dev was indeed missing, but configure > still wants to build r :-( Martin > > > > > > Martin > > > > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: > >> > >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release > >> wrote: > >> > > >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: > >> >> > >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release > >> >> wrote: > >> >> > > >> >> > Thanks again! It still tries to build R and fails > >> >> > > >> >> > I checked that system R starts, it does (R version 3.4.4) > >> >> Please also make sure that > >> >> > >> >> pkg-config --modversion libR > >> >> > >> >> outputs the version. > >> >> > >> > Yes, it does. > >> > > >> >> > >> >> However there is just no "checking for R" message in your > config.log, > >> >> it indicates that there are still remains of R left > >> >> in your installation. > >> >> > >> >> I've opened https://trac.sagemath.org/ticket/29016 > >> >> to deal with R being hard to clean away - feel free to try it. > >> >> > >> >> Maybe you also need to run > >> >> > >> >> make r-clean > >> > > >> > > >> > I did that, it says that there is no legacy uninstaller for r, and > that there is nothing to do. I checked for the files in the ticket, but > none of them exists. :-( > >> > > >> > The config.log contains the lines > >> > > >> > configure:18950: checking installing any of atlas openblas iconv > readline bzip2 xz pcre curl? > >> > configure:18954: result: yes; install r as well > >> > > >> > but I do not know how to find out which of those (atlas openblas > iconv readline bzip2 xz pcre curl) is the problem. > >> > >> The easiest is to look at the output of ./configure > >> It should contain lines like > >> > >> atlas-3.10.2.p3 will not be installed (configure check) > >> > >> for each of the packages in that list. > >> So for any of these that are not marked this way, please install the > >> corresponding system package > >> and re-run configure. > >> > >> > >> > >> > > >> > Martin > >> > > >> > -- > >> > 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-r...@googlegroups.com. > >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.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/a2512246-f441-4ace-82df-fd1f354bcaf5%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Wed, Jan 15, 2020 at 12:13 PM 'Martin R' via sage-release wrote: > > Oh dea, this is becoming strange: > > The output of configure says that > > atlas, openblas, iconv will NOT be installed, but > > bzip2-1.0.6-20150304.p0 > readline-6.3.008.p0 > xz-5.2.2.p0 > pcre-8.40.p2 > curl-7.62.0.p0 > > However, I certainly have bzip2, xz, pcre and curl on my system, and I guess > also readline. > > Might there be a bug in configure? You need development versions of these, see https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation So, on Ubuntu: libbz2-dev libreadline-dev (seems to be missing in docs) liblzma-dev (this is the xz lib, iirc) libpcre3-dev libcurl4-openssl-dev > > Martin > > Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release >> wrote: >> > >> > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >> >> wrote: >> >> > >> >> > Thanks again! It still tries to build R and fails >> >> > >> >> > I checked that system R starts, it does (R version 3.4.4) >> >> Please also make sure that >> >> >> >> pkg-config --modversion libR >> >> >> >> outputs the version. >> >> >> > Yes, it does. >> > >> >> >> >> However there is just no "checking for R" message in your config.log, >> >> it indicates that there are still remains of R left >> >> in your installation. >> >> >> >> I've opened https://trac.sagemath.org/ticket/29016 >> >> to deal with R being hard to clean away - feel free to try it. >> >> >> >> Maybe you also need to run >> >> >> >> make r-clean >> > >> > >> > I did that, it says that there is no legacy uninstaller for r, and that >> > there is nothing to do. I checked for the files in the ticket, but none >> > of them exists. :-( >> > >> > The config.log contains the lines >> > >> > configure:18950: checking installing any of atlas openblas iconv readline >> > bzip2 xz pcre curl? >> > configure:18954: result: yes; install r as well >> > >> > but I do not know how to find out which of those (atlas openblas iconv >> > readline bzip2 xz pcre curl) is the problem. >> >> The easiest is to look at the output of ./configure >> It should contain lines like >> >> atlas-3.10.2.p3 will not be installed (configure check) >> >> for each of the packages in that list. >> So for any of these that are not marked this way, please install the >> corresponding system package >> and re-run configure. >> >> >> >> > >> > Martin >> > >> > -- >> > 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-r...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.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/CAAWYfq0NkisLvB%2B7fq5eks-js239wvgRw8Kb1WhMMrZVrn-MgA%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
Oh dea, this is becoming strange: The output of configure says that atlas, openblas, iconv will NOT be installed, but bzip2-1.0.6-20150304.p0 readline-6.3.008.p0 xz-5.2.2.p0 pcre-8.40.p2 curl-7.62.0.p0 However, I certainly have bzip2, xz, pcre and curl on my system, and I guess also readline. Might there be a bug in configure? Martin Am Mittwoch, 15. Januar 2020 13:00:51 UTC+1 schrieb Dima Pasechnik: > > On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release > > wrote: > > > > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: > >> > >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release > >> wrote: > >> > > >> > Thanks again! It still tries to build R and fails > >> > > >> > I checked that system R starts, it does (R version 3.4.4) > >> Please also make sure that > >> > >> pkg-config --modversion libR > >> > >> outputs the version. > >> > > Yes, it does. > > > >> > >> However there is just no "checking for R" message in your config.log, > >> it indicates that there are still remains of R left > >> in your installation. > >> > >> I've opened https://trac.sagemath.org/ticket/29016 > >> to deal with R being hard to clean away - feel free to try it. > >> > >> Maybe you also need to run > >> > >> make r-clean > > > > > > I did that, it says that there is no legacy uninstaller for r, and that > there is nothing to do. I checked for the files in the ticket, but none of > them exists. :-( > > > > The config.log contains the lines > > > > configure:18950: checking installing any of atlas openblas iconv > readline bzip2 xz pcre curl? > > configure:18954: result: yes; install r as well > > > > but I do not know how to find out which of those (atlas openblas iconv > readline bzip2 xz pcre curl) is the problem. > > The easiest is to look at the output of ./configure > It should contain lines like > > atlas-3.10.2.p3 will not be installed (configure check) > > for each of the packages in that list. > So for any of these that are not marked this way, please install the > corresponding system package > and re-run configure. > > > > > > > Martin > > > > -- > > 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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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/ca07b5bd-8fe6-4383-ad3a-eab749b3760e%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Wed, Jan 15, 2020 at 11:35 AM 'Martin R' via sage-release wrote: > > Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release >> wrote: >> > >> > Thanks again! It still tries to build R and fails >> > >> > I checked that system R starts, it does (R version 3.4.4) >> Please also make sure that >> >> pkg-config --modversion libR >> >> outputs the version. >> > Yes, it does. > >> >> However there is just no "checking for R" message in your config.log, >> it indicates that there are still remains of R left >> in your installation. >> >> I've opened https://trac.sagemath.org/ticket/29016 >> to deal with R being hard to clean away - feel free to try it. >> >> Maybe you also need to run >> >> make r-clean > > > I did that, it says that there is no legacy uninstaller for r, and that there > is nothing to do. I checked for the files in the ticket, but none of them > exists. :-( > > The config.log contains the lines > > configure:18950: checking installing any of atlas openblas iconv readline > bzip2 xz pcre curl? > configure:18954: result: yes; install r as well > > but I do not know how to find out which of those (atlas openblas iconv > readline bzip2 xz pcre curl) is the problem. The easiest is to look at the output of ./configure It should contain lines like atlas-3.10.2.p3 will not be installed (configure check) for each of the packages in that list. So for any of these that are not marked this way, please install the corresponding system package and re-run configure. > > Martin > > -- > 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/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.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/CAAWYfq3R4b7cbfZtdTD4-zUu28dVJ-AmDx1f9kWnmQzdBnoDUQ%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
Am Mittwoch, 15. Januar 2020 12:02:30 UTC+1 schrieb Dima Pasechnik: > > On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release > > wrote: > > > > Thanks again! It still tries to build R and fails > > > > I checked that system R starts, it does (R version 3.4.4) > Please also make sure that > > pkg-config --modversion libR > > outputs the version. > > Yes, it does. > However there is just no "checking for R" message in your config.log, > it indicates that there are still remains of R left > in your installation. > > I've opened https://trac.sagemath.org/ticket/29016 > to deal with R being hard to clean away - feel free to try it. > > Maybe you also need to run > > make r-clean > I did that, it says that there is no legacy uninstaller for r, and that there is nothing to do. I checked for the files in the ticket, but none of them exists. :-( The config.log contains the lines configure:18950: checking installing any of atlas openblas iconv readline bzip2 xz pcre curl? configure:18954: result: yes; install r as well but I do not know how to find out which of those (atlas openblas iconv readline bzip2 xz pcre curl) is the problem. Martin -- 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/5d105000-cea2-48a5-8840-aeb405a6cb71%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Wed, Jan 15, 2020 at 10:37 AM 'Martin R' via sage-release wrote: > > Thanks again! It still tries to build R and fails > > I checked that system R starts, it does (R version 3.4.4) Please also make sure that pkg-config --modversion libR outputs the version. However there is just no "checking for R" message in your config.log, it indicates that there are still remains of R left in your installation. I've opened https://trac.sagemath.org/ticket/29016 to deal with R being hard to clean away - feel free to try it. Maybe you also need to run make r-clean > > The new config.log is attached. > > Sorry and thank you! > > Am Mittwoch, 15. Januar 2020 11:13:09 UTC+1 schrieb Dima Pasechnik: >> >> It seems you have remains of an old R installation in local/ >> So you need >> rm -rf local/lib/R >> rm local/bin/R* >> >> and then re-run ./configure >> >> (details ar in https://trac.sagemath.org/ticket/28884) >> >> >> On Wed, Jan 15, 2020 at 10:01 AM 'Martin R' via sage-release >> wrote: >> > >> > Many thanks for your help - unfortunately it didn't work though. >> > >> > I am attaching the new config.log >> > >> > Martin >> > >> > Am Mittwoch, 15. Januar 2020 10:19:35 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release >> >> wrote: >> >> > >> >> > Dear all, >> >> > >> >> > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build >> >> > (incremental from a relatiively recent release, but I don't remember >> >> > which) on Ubuntu 18.04.3, and I have absolutely no clue. The last bit >> >> > oortunatf the error message is >> >> > >> >> The R problem is known, and related to recent gfortran releases. >> >> https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/ >> >> >> >> You might instead install openblas and R from the system, they should >> >> be recognised. >> >> (also gsl, cliquer, so, for Ubuntu, `apt-get libopenblas-dev >> >> r-base-dev libgsl-dev libcliquer-dev cliquer`) >> >> as well as `make openblas-clean gsl-clean cliquer-clean` >> >> before ./configure && make build >> >> >> >> >> >> >> >> > [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed >> >> > [r-3.6.2] make[7]: *** [integrate.o] Error 1 >> >> > >> >> > sage starts and is otherwise usable. >> >> > >> >> > The log is attached. It would be great if I could avoid rebuilding all >> >> > of sage, because this is an old laptop... >> >> > >> >> > Many many thanks, >> >> > >> >> > Martin >> >> > >> >> > -- >> >> > 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-r...@googlegroups.com. >> >> > To view this discussion on the web visit >> >> > https://groups.google.com/d/msgid/sage-release/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.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-r...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-release/a6968f7e-4e2f-49db-98a7-881d07d98b79%40googlegroups.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/b3ac82ee-13d4-4a8b-8b16-9dd6b2aa8014%40googlegroups.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/CAAWYfq1o30_pgTbYKkxnSv9SU86rwtE9cjQPnAtANSwWCJD1BQ%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
Thanks again! It still tries to build R and fails I checked that system R starts, it does (R version 3.4.4) The new config.log is attached. Sorry and thank you! Am Mittwoch, 15. Januar 2020 11:13:09 UTC+1 schrieb Dima Pasechnik: > > It seems you have remains of an old R installation in local/ > So you need > rm -rf local/lib/R > rm local/bin/R* > > and then re-run ./configure > > (details ar in https://trac.sagemath.org/ticket/28884) > > > On Wed, Jan 15, 2020 at 10:01 AM 'Martin R' via sage-release > > wrote: > > > > Many thanks for your help - unfortunately it didn't work though. > > > > I am attaching the new config.log > > > > Martin > > > > Am Mittwoch, 15. Januar 2020 10:19:35 UTC+1 schrieb Dima Pasechnik: > >> > >> On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release > >> wrote: > >> > > >> > Dear all, > >> > > >> > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build > (incremental from a relatiively recent release, but I don't remember which) > on Ubuntu 18.04.3, and I have absolutely no clue. The last bit oortunatf > the error message is > >> > > >> The R problem is known, and related to recent gfortran releases. > >> > https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/ > > >> > >> You might instead install openblas and R from the system, they should > >> be recognised. > >> (also gsl, cliquer, so, for Ubuntu, `apt-get libopenblas-dev > >> r-base-dev libgsl-dev libcliquer-dev cliquer`) > >> as well as `make openblas-clean gsl-clean cliquer-clean` > >> before ./configure && make build > >> > >> > >> > >> > [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed > >> > [r-3.6.2] make[7]: *** [integrate.o] Error 1 > >> > > >> > sage starts and is otherwise usable. > >> > > >> > The log is attached. It would be great if I could avoid rebuilding > all of sage, because this is an old laptop... > >> > > >> > Many many thanks, > >> > > >> > Martin > >> > > >> > -- > >> > 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-r...@googlegroups.com. > >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/a6968f7e-4e2f-49db-98a7-881d07d98b79%40googlegroups.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/b3ac82ee-13d4-4a8b-8b16-9dd6b2aa8014%40googlegroups.com. This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Sage configure 9.1.beta0, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --with-python=2 ## - ## ## Platform. ## ## - ## hostname = Martin-Laptop uname -m = x86_64 uname -r = 4.15.0-74-generic uname -s = Linux uname -v = #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/martin/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /usr/local/games PATH: /snap/bin ## --- ## ## Core tests. ## ## --- ## configure:3148: checking for a BSD-compatible install configure:3216: result: /usr/bin/install -c configure:3227: checking whether build environment is sane configure:3282: result: yes configure:3433: checking for a thread-safe mkdir -p configure:3472: result: /bin/mkdir -p configure:3479: checking for gawk configure:3495: found /usr/bin/gawk configure:3506: result: gawk configure:3517: checking whether make sets $(MAKE) configure:3539: result: yes configure:3568: checking whether make supports nested variables configure:3585: result: yes configure:3714: checking whether to enable maintainer-specific portions of Makefiles configure:3723: result: yes configure:3774: checking for root user configure:3783: result: no configure:3795: checking build system type configure:3809: result: x86_64-pc-linux-gnu
Re: [sage-release] Re: Sage 9.1.beta0 released
It seems you have remains of an old R installation in local/ So you need rm -rf local/lib/R rm local/bin/R* and then re-run ./configure (details ar in https://trac.sagemath.org/ticket/28884) On Wed, Jan 15, 2020 at 10:01 AM 'Martin R' via sage-release wrote: > > Many thanks for your help - unfortunately it didn't work though. > > I am attaching the new config.log > > Martin > > Am Mittwoch, 15. Januar 2020 10:19:35 UTC+1 schrieb Dima Pasechnik: >> >> On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release >> wrote: >> > >> > Dear all, >> > >> > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build >> > (incremental from a relatiively recent release, but I don't remember >> > which) on Ubuntu 18.04.3, and I have absolutely no clue. The last bit >> > oortunatf the error message is >> > >> The R problem is known, and related to recent gfortran releases. >> https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/ >> >> You might instead install openblas and R from the system, they should >> be recognised. >> (also gsl, cliquer, so, for Ubuntu, `apt-get libopenblas-dev >> r-base-dev libgsl-dev libcliquer-dev cliquer`) >> as well as `make openblas-clean gsl-clean cliquer-clean` >> before ./configure && make build >> >> >> >> > [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed >> > [r-3.6.2] make[7]: *** [integrate.o] Error 1 >> > >> > sage starts and is otherwise usable. >> > >> > The log is attached. It would be great if I could avoid rebuilding all of >> > sage, because this is an old laptop... >> > >> > Many many thanks, >> > >> > Martin >> > >> > -- >> > 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-r...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-release/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.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/a6968f7e-4e2f-49db-98a7-881d07d98b79%40googlegroups.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/CAAWYfq2niV8cHbof8QgmCL17GwDk-FHcx%2B4YqtwFe_Ddky0tzQ%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
Many thanks for your help - unfortunately it didn't work though. I am attaching the new config.log Martin Am Mittwoch, 15. Januar 2020 10:19:35 UTC+1 schrieb Dima Pasechnik: > > On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release > > wrote: > > > > Dear all, > > > > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build > (incremental from a relatiively recent release, but I don't remember which) > on Ubuntu 18.04.3, and I have absolutely no clue. The last bit oortunatf > the error message is > > > The R problem is known, and related to recent gfortran releases. > > https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/ > > > You might instead install openblas and R from the system, they should > be recognised. > (also gsl, cliquer, so, for Ubuntu, `apt-get libopenblas-dev > r-base-dev libgsl-dev libcliquer-dev cliquer`) > as well as `make openblas-clean gsl-clean cliquer-clean` > before ./configure && make build > > > > > [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed > > [r-3.6.2] make[7]: *** [integrate.o] Error 1 > > > > sage starts and is otherwise usable. > > > > The log is attached. It would be great if I could avoid rebuilding all > of sage, because this is an old laptop... > > > > Many many thanks, > > > > Martin > > > > -- > > 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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.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/a6968f7e-4e2f-49db-98a7-881d07d98b79%40googlegroups.com. This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Sage configure 9.1.beta0, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --with-python=2 ## - ## ## Platform. ## ## - ## hostname = Martin-Laptop uname -m = x86_64 uname -r = 4.15.0-74-generic uname -s = Linux uname -v = #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/martin/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /usr/local/games PATH: /snap/bin ## --- ## ## Core tests. ## ## --- ## configure:3148: checking for a BSD-compatible install configure:3216: result: /usr/bin/install -c configure:3227: checking whether build environment is sane configure:3282: result: yes configure:3433: checking for a thread-safe mkdir -p configure:3472: result: /bin/mkdir -p configure:3479: checking for gawk configure:3495: found /usr/bin/gawk configure:3506: result: gawk configure:3517: checking whether make sets $(MAKE) configure:3539: result: yes configure:3568: checking whether make supports nested variables configure:3585: result: yes configure:3714: checking whether to enable maintainer-specific portions of Makefiles configure:3723: result: yes configure:3774: checking for root user configure:3783: result: no configure:3795: checking build system type configure:3809: result: x86_64-pc-linux-gnu configure:3829: checking host system type configure:3842: result: x86_64-pc-linux-gnu configure:3954: checking for a sed that does not truncate output configure:4018: result: /bin/sed configure:4026: checking for ar configure:4042: found /usr/bin/ar configure:4054: result: yes configure:4075: checking for m4 configure:4091: found /usr/bin/m4 configure:4103: result: yes configure:4178: checking for pkg-config configure:4196: found /usr/bin/pkg-config configure:4208: result: /usr/bin/pkg-config configure:4233: checking pkg-config is at least version 0.9.0 configure:4236: result: yes configure:4247: checking for ranlib configure:4263: found /usr/bin/ranlib configure:4275: result: yes configure:4296: checking for strip configure:4312: found /usr/bin/strip configure:4324: result: yes configure:4344: checking for GNU or BSD tar configure:4392: result: /bin/tar configure:4403: checking for GNU make configure:4445: result: /usr/bin/make configure:4459: checking for latex configure:4475: found /usr/bin/latex configure:4487: result: yes configure:4511: checking for perl
Re: [sage-release] Re: Sage 9.1.beta0 released
Thanks for the help. I upgraded devtoolset to 7, but it is still pkg-config 0.27.1 there. So that didn't help. Markus' suggestion solved it. Chris -- 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/825eef3a-d263-42ee-8af1-1a591a5ff35d%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Wed, Jan 15, 2020 at 9:12 AM 'Martin R' via sage-release wrote: > > Dear all, > > I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build (incremental > from a relatiively recent release, but I don't remember which) on Ubuntu > 18.04.3, and I have absolutely no clue. The last bit of the error message is > The R problem is known, and related to recent gfortran releases. https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/ You might instead install openblas and R from the system, they should be recognised. (also gsl, cliquer, so, for Ubuntu, `apt-get libopenblas-dev r-base-dev libgsl-dev libcliquer-dev cliquer`) as well as `make openblas-clean gsl-clean cliquer-clean` before ./configure && make build > [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed > [r-3.6.2] make[7]: *** [integrate.o] Error 1 > > sage starts and is otherwise usable. > > The log is attached. It would be great if I could avoid rebuilding all of > sage, because this is an old laptop... > > Many many thanks, > > Martin > > -- > 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/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.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/CAAWYfq2Ca_8SMznetQ%3DHimZ1_vMfxZrOZXtaY%3DrQYMHW9ZvpCA%40mail.gmail.com.
[sage-release] Re: Sage 9.1.beta0 released
Dear all, I have a problem with r-3.6.2 in 9.1.beta0 in an python2 build (incremental from a relatiively recent release, but I don't remember which) on Ubuntu 18.04.3, and I have absolutely no clue. The last bit of the error message is [r-3.6.2] ../../Makeconf:124: recipe for target 'integrate.o' failed [r-3.6.2] make[7]: *** [integrate.o] Error 1 sage starts and is otherwise usable. The log is attached. It would be great if I could avoid rebuilding all of sage, because this is an old laptop... Many many thanks, Martin -- 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/0c30ee50-2f00-4ec2-88cd-05ac3cb282b0%40googlegroups.com. Found local metadata for r-3.6.2 Using cached file /home/martin/sage-develop/upstream/R-3.6.2.tar.gz r-3.6.2 Setting up build directory for r-3.6.2 Finished extraction Applying patches from ../patches... Applying ../patches/autoconf_verb_dash.patch patching file configure Hunk #1 succeeded at 24966 with fuzz 2 (offset 129 lines). Hunk #2 succeeded at 25323 (offset 130 lines). Applying ../patches/cygwin_build_support.patch patching file configure Hunk #1 succeeded at 27637 (offset -86 lines). Hunk #2 succeeded at 27879 (offset -117 lines). Hunk #3 succeeded at 27892 (offset -117 lines). Hunk #4 succeeded at 27905 (offset -117 lines). patching file configure.ac Hunk #1 succeeded at 1280 (offset -14 lines). Hunk #2 succeeded at 1537 (offset -14 lines). Hunk #3 succeeded at 1549 (offset -14 lines). Hunk #4 succeeded at 1561 (offset -14 lines). patching file src/library/tools/R/install.R Hunk #1 succeeded at 1215 (offset 374 lines). Applying ../patches/hardcoded_dirs.patch patching file src/scripts/Makefile.in Hunk #1 succeeded at 87 (offset -2 lines). patching file src/scripts/R.sh.in Applying ../patches/libcurl_https_support.patch patching file configure Hunk #1 succeeded at 42943 (offset 1874 lines). Hunk #2 succeeded at 42952 (offset 1874 lines). patching file m4/R.m4 Hunk #1 succeeded at 4181 (offset -24 lines). Applying ../patches/link_all_shared_libs.patch patching file etc/Makeconf.in Hunk #1 succeeded at 159 with fuzz 2 (offset 9 lines). Applying ../patches/m4_macro_bug.patch patching file configure Hunk #1 succeeded at 42543 (offset 1744 lines). Hunk #2 succeeded at 42587 with fuzz 2 (offset 1744 lines). patching file m4/R.m4 Hunk #1 succeeded at 3100 (offset -90 lines). Hunk #2 succeeded at 3122 with fuzz 2 (offset -90 lines). Applying ../patches/rcmd_exec.patch patching file src/scripts/Rcmd.in Host system: Linux Martin-Laptop 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) Package 'r' is currently not installed No legacy uninstaller found for 'r'; nothing to do R_CONFIGURE_BLAS=--with-blas=-L/home/martin/sage-develop/local/lib -lopenblas R_CONFIGURE_LAPACK=--with-lapack=-L/home/martin/sage-develop/local/lib -lopenblas checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu loading site script './config.site' loading build-specific script './config.site' checking for pwd... /bin/pwd checking whether builddir is srcdir... yes checking whether ln -s works... yes checking for ar... ar
Re: [sage-release] Re: Sage 9.1.beta0 released
For now, `./bootstrap -D` can be used as a workaround for this problem. Am Dienstag, 14. Januar 2020 12:24:57 UTC+1 schrieb Dima Pasechnik: > > On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich > > wrote: > > > > > > > > make build after pulling 9.1.beta0 produces an error below. I have no > problems compiling 9.0. > > This is on centos 7 with devtoolset-4 enabled. > > Sorry if this is noise produced by me making an error. Happy to provide > any other information. > > > > make -j4 build/make/Makefile --stop > > make[1]: Entering directory `/local/pmzcw/prog/sage' > > ./bootstrap -d > > make[2]: Entering directory `/local/pmzcw/prog/sage' > > rm -rf config configure build/make/Makefile-auto.in > > make[2]: Leaving directory `/local/pmzcw/prog/sage' > > bootstrap:69: installing 'config/config.rpath' > > configure.ac:113: installing 'config/config.guess' > > configure.ac:113: installing 'config/config.sub' > > configure.ac:68: installing 'config/install-sh' > > configure.ac:68: installing 'config/missing' > > configure.ac:453: error: possibly undefined macro: AC_CONFIG_COMMANDS > > If this token and others are legitimate, please use > m4_pattern_allow. > > See the Autoconf documentation. > > configure:10801: error: possibly undefined macro: PKG_CHECK_VAR > > configure:10802: error: possibly undefined macro: AC_CONFIG_LINKS > > configure:10807: error: possibly undefined macro: AC_MSG_WARN > > > > > > make dist-clean also fails with > > > > checking BLAS library... openblas > > ./configure: line 10801: syntax error near unexpected token > `OPENBLASPCDIR,' > > ./configure: line 10801: `PKG_CHECK_VAR(OPENBLASPCDIR, openblas, > pcfiledir,' > > If you would like to try to build Sage anyway (to help porting), > > export the variable 'SAGE_PORT' to something non-empty. > > make[1]: *** [build/make/Makefile] Error 1 > > make[1]: Leaving directory `/local/pmzcw/prog/sage' > > make: *** [dist-clean] Error 2 > > the latter is https://trac.sagemath.org/ticket/29001 > > (perhaps the former too, not sure) > > > > > > > Chris > > > > -- > > 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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/6726a7ab-37c3-423d-bf28-1fd5e764e478%40googlegroups.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/8f402173-93d9-46b1-9087-5e91be645100%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich wrote: > > > > make build after pulling 9.1.beta0 produces an error below. I have no > problems compiling 9.0. > This is on centos 7 with devtoolset-4 enabled. https://www.softwarecollections.org/en/scls/rhscl/devtoolset-4/ says that devtoolset-4 is officially dead, since Dec 2017. Can you move to something newer, e.g. devtoolset-7 ? > Sorry if this is noise produced by me making an error. Happy to provide any > other information. > > make -j4 build/make/Makefile --stop > make[1]: Entering directory `/local/pmzcw/prog/sage' > ./bootstrap -d > make[2]: Entering directory `/local/pmzcw/prog/sage' > rm -rf config configure build/make/Makefile-auto.in > make[2]: Leaving directory `/local/pmzcw/prog/sage' > bootstrap:69: installing 'config/config.rpath' > configure.ac:113: installing 'config/config.guess' > configure.ac:113: installing 'config/config.sub' > configure.ac:68: installing 'config/install-sh' > configure.ac:68: installing 'config/missing' > configure.ac:453: error: possibly undefined macro: AC_CONFIG_COMMANDS > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure:10801: error: possibly undefined macro: PKG_CHECK_VAR > configure:10802: error: possibly undefined macro: AC_CONFIG_LINKS > configure:10807: error: possibly undefined macro: AC_MSG_WARN > > > make dist-clean also fails with > > checking BLAS library... openblas > ./configure: line 10801: syntax error near unexpected token `OPENBLASPCDIR,' > ./configure: line 10801: `PKG_CHECK_VAR(OPENBLASPCDIR, openblas, > pcfiledir,' > If you would like to try to build Sage anyway (to help porting), > export the variable 'SAGE_PORT' to something non-empty. > make[1]: *** [build/make/Makefile] Error 1 > make[1]: Leaving directory `/local/pmzcw/prog/sage' > make: *** [dist-clean] Error 2 > > > Chris > > -- > 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/6726a7ab-37c3-423d-bf28-1fd5e764e478%40googlegroups.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/CAAWYfq3DteKrvJD2yiCmMFtrnuvngOCy9A_nRjWa3Jf1pptWAg%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.1.beta0 released
On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich wrote: > > > > make build after pulling 9.1.beta0 produces an error below. I have no > problems compiling 9.0. > This is on centos 7 with devtoolset-4 enabled. > Sorry if this is noise produced by me making an error. Happy to provide any > other information. > > make -j4 build/make/Makefile --stop > make[1]: Entering directory `/local/pmzcw/prog/sage' > ./bootstrap -d > make[2]: Entering directory `/local/pmzcw/prog/sage' > rm -rf config configure build/make/Makefile-auto.in > make[2]: Leaving directory `/local/pmzcw/prog/sage' > bootstrap:69: installing 'config/config.rpath' > configure.ac:113: installing 'config/config.guess' > configure.ac:113: installing 'config/config.sub' > configure.ac:68: installing 'config/install-sh' > configure.ac:68: installing 'config/missing' > configure.ac:453: error: possibly undefined macro: AC_CONFIG_COMMANDS > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure:10801: error: possibly undefined macro: PKG_CHECK_VAR > configure:10802: error: possibly undefined macro: AC_CONFIG_LINKS > configure:10807: error: possibly undefined macro: AC_MSG_WARN > > > make dist-clean also fails with > > checking BLAS library... openblas > ./configure: line 10801: syntax error near unexpected token `OPENBLASPCDIR,' > ./configure: line 10801: `PKG_CHECK_VAR(OPENBLASPCDIR, openblas, > pcfiledir,' > If you would like to try to build Sage anyway (to help porting), > export the variable 'SAGE_PORT' to something non-empty. > make[1]: *** [build/make/Makefile] Error 1 > make[1]: Leaving directory `/local/pmzcw/prog/sage' > make: *** [dist-clean] Error 2 the latter is https://trac.sagemath.org/ticket/29001 (perhaps the former too, not sure) > > > Chris > > -- > 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/6726a7ab-37c3-423d-bf28-1fd5e764e478%40googlegroups.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/CAAWYfq1%3DwAwCyDVroh0h%2BzTLjhz5OtDH%3DM987diiVoyQ%3DFsdBw%40mail.gmail.com.
[sage-release] Re: Sage 9.1.beta0 released
make build after pulling 9.1.beta0 produces an error below. I have no problems compiling 9.0. This is on centos 7 with devtoolset-4 enabled. Sorry if this is noise produced by me making an error. Happy to provide any other information. make -j4 build/make/Makefile --stop make[1]: Entering directory `/local/pmzcw/prog/sage' ./bootstrap -d make[2]: Entering directory `/local/pmzcw/prog/sage' rm -rf config configure build/make/Makefile-auto.in make[2]: Leaving directory `/local/pmzcw/prog/sage' bootstrap:69: installing 'config/config.rpath' configure.ac:113: installing 'config/config.guess' configure.ac:113: installing 'config/config.sub' configure.ac:68: installing 'config/install-sh' configure.ac:68: installing 'config/missing' configure.ac:453: error: possibly undefined macro: AC_CONFIG_COMMANDS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:10801: error: possibly undefined macro: PKG_CHECK_VAR configure:10802: error: possibly undefined macro: AC_CONFIG_LINKS configure:10807: error: possibly undefined macro: AC_MSG_WARN make dist-clean also fails with checking BLAS library... openblas ./configure: line 10801: syntax error near unexpected token `OPENBLASPCDIR,' ./configure: line 10801: `PKG_CHECK_VAR(OPENBLASPCDIR, openblas, pcfiledir,' If you would like to try to build Sage anyway (to help porting), export the variable 'SAGE_PORT' to something non-empty. make[1]: *** [build/make/Makefile] Error 1 make[1]: Leaving directory `/local/pmzcw/prog/sage' make: *** [dist-clean] Error 2 Chris -- 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/6726a7ab-37c3-423d-bf28-1fd5e764e478%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
On Ubuntu 18.04 running on a bi-Xeon E5-2623 (8 cores) + 16 GB RAM computer: - build (with -j16) from a fresh git clone + pull develop: OK - all tests from ptestlong passed Eric -- 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/cf676832-f42b-4fd2-8d7f-4f28c43f1edb%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
All segmentation faults vanished! But new were introduced: ./sage -t --long src/sage/modular/btquotients/pautomorphicform.py # Timed out -> again ./sage -t --long src/sage/rings/finite_rings/residue_field.pyx # Timed out -> All tests passed ./sage -t --long src/sage/schemes/elliptic_curves/constructor.py # Timed out -> again ./sage -t --long src/sage/schemes/elliptic_curves/gal_reps.py # Timed out -> Segmentation fault! ./sage -t --long src/sage/schemes/elliptic_curves/ell_torsion.py # Timed out -> Segmentation fault ./sage -t --long src/sage/schemes/affine/affine_morphism.py # Timed out -> again ./sage -t --long src/sage/rings/morphism.pyx # Timed out -> Segmentation fault I saved the output of: bash failures > failure.log 2>&1 & Anyone interested? There were 3 'normal' test failures. Also present in sage-9.0. Ten days ago I made trac tickets: #28939, #28940 and #28941. On Saturday, January 11, 2020 at 2:09:24 PM UTC+1, Emmanuel Charpentier wrote: > > What happens when you re-run these failed test standalone (i. e. one at a > time) ? > > Le samedi 11 janvier 2020 13:59:09 UTC+1, Jaap Spies a écrit : >> >> On Rasbian (see below) >> >> make ptestlong ended with: >> >> -- >> Total time for all tests: 28699.4 seconds >> cpu time: 41119.9 seconds >> cumulative wall time: 51721.1 seconds >> make: *** [Makefile:178: ptestlong] Error 21 >> >> Some or most will be transient failures? I'll check. >> -- >> sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Killed >> due to segmentation fault >> sage -t --long src/sage/modular/btquotients/pautomorphicform.py # Timed >> out >> sage -t --long src/sage/rings/finite_rings/residue_field.pyx # Timed out >> sage -t --long src/sage/schemes/elliptic_curves/constructor.py # Timed >> out >> sage -t --long src/sage/schemes/elliptic_curves/gal_reps.py # Timed out >> sage -t --long src/sage/rings/function_field/function_field.py # Timed >> out >> sage -t --long src/sage/structure/coerce_dict.pyx # 1 doctest failed >> sage -t --long src/sage/manifolds/differentiable/mixed_form.py # Killed >> due to segmentation fault >> sage -t --long >> src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py # Timed >> out >> sage -t --long src/sage/combinat/tableau.py # Killed due to segmentation >> fault >> sage -t --long src/sage/combinat/designs/database.py # Timed out >> sage -t --long src/sage/graphs/strongly_regular_db.pyx # Killed due to >> segmentation fault >> sage -t --long src/sage/modular/hypergeometric_motive.py # Timed out >> sage -t --long >> src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # Timed out >> sage -t --long src/sage/categories/pushout.py # Timed out >> sage -t --long src/sage/modular/btquotients/btquotient.py # Timed out >> sage -t --long src/sage/rings/function_field/differential.py # Killed >> due to segmentation fault >> sage -t --long src/sage/rings/valuation/valuation.py # Timed out >> sage -t --long src/sage/schemes/toric/sheaf/klyachko.py # Timed out >> sage -t --long src/sage/modular/pollack_stevens/padic_lseries.py # Timed >> out >> sage -t --long src/sage/combinat/ncsym/ncsym.py # Killed due to >> segmentation fault >> sage -t --long src/sage/misc/c3_controlled.pyx # Killed due to >> segmentation fault >> sage -t --long src/sage/modular/local_comp/smoothchar.py # Timed out >> sage -t --long src/sage/combinat/designs/block_design.py # Timed out >> sage -t --long src/sage/rings/function_field/function_field_valuation.py >> # Timed out >> sage -t --long src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx >> # Timed out >> sage -t --long src/sage/schemes/elliptic_curves/ell_torsion.py # Timed >> out >> sage -t --long src/sage/combinat/sf/orthotriang.py # Killed due to >> segmentation fault >> sage -t --long src/sage/modular/modform/tests.py # Killed due to >> segmentation fault >> sage -t --long src/sage/schemes/curves/constructor.py # Killed due to >> segmentation fault >> sage -t --long src/sage/combinat/sf/powersum.py # Killed due to >> segmentation fault >> sage -t --long src/sage/matrix/matrix_cyclo_dense.pyx # Timed out >> sage -t --long src/sage/schemes/affine/affine_morphism.py # Timed out >> sage -t --long src/sage/quivers/homspace.py # Killed due to segmentation >> fault >> sage -t --long src/sage/rings/finite_rings/finite_field_prime_modn.py # >> Killed due to segmentation fault >> sage -t --long src/sage/rings/morphism.pyx # Timed out >> sage -t --long src/sage/rings/padics/relative_extension_leaves.py # >> Timed out >> sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed >> sage -t --long src/sage/coding/reed_muller_code.py # Timed out >> sage -t --long src/doc/en/constructions/elliptic_curves.rst # Timed out >> sage -t --long
[sage-release] Re: Sage 9.1.beta0 released
2017 MacBook Pro, 10.14.6, make: > Sage build/upgrade complete! make ptestlong: > -- > All tests passed! > -- > Total time for all tests: 3997.5 seconds > cpu time: 18884.2 seconds > cumulative wall time: 30655.4 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/d65ab1d7-186c-4367-9895-d8e172e5dd37%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
What happens when you re-run these failed test standalone (i. e. one at a time) ? Le samedi 11 janvier 2020 13:59:09 UTC+1, Jaap Spies a écrit : > > On Rasbian (see below) > > make ptestlong ended with: > > -- > Total time for all tests: 28699.4 seconds > cpu time: 41119.9 seconds > cumulative wall time: 51721.1 seconds > make: *** [Makefile:178: ptestlong] Error 21 > > Some or most will be transient failures? I'll check. > -- > sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Killed > due to segmentation fault > sage -t --long src/sage/modular/btquotients/pautomorphicform.py # Timed > out > sage -t --long src/sage/rings/finite_rings/residue_field.pyx # Timed out > sage -t --long src/sage/schemes/elliptic_curves/constructor.py # Timed out > sage -t --long src/sage/schemes/elliptic_curves/gal_reps.py # Timed out > sage -t --long src/sage/rings/function_field/function_field.py # Timed out > sage -t --long src/sage/structure/coerce_dict.pyx # 1 doctest failed > sage -t --long src/sage/manifolds/differentiable/mixed_form.py # Killed > due to segmentation fault > sage -t --long > src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py # Timed > out > sage -t --long src/sage/combinat/tableau.py # Killed due to segmentation > fault > sage -t --long src/sage/combinat/designs/database.py # Timed out > sage -t --long src/sage/graphs/strongly_regular_db.pyx # Killed due to > segmentation fault > sage -t --long src/sage/modular/hypergeometric_motive.py # Timed out > sage -t --long src/sage/schemes/cyclic_covers/cycliccover_finite_field.py > # Timed out > sage -t --long src/sage/categories/pushout.py # Timed out > sage -t --long src/sage/modular/btquotients/btquotient.py # Timed out > sage -t --long src/sage/rings/function_field/differential.py # Killed due > to segmentation fault > sage -t --long src/sage/rings/valuation/valuation.py # Timed out > sage -t --long src/sage/schemes/toric/sheaf/klyachko.py # Timed out > sage -t --long src/sage/modular/pollack_stevens/padic_lseries.py # Timed > out > sage -t --long src/sage/combinat/ncsym/ncsym.py # Killed due to > segmentation fault > sage -t --long src/sage/misc/c3_controlled.pyx # Killed due to > segmentation fault > sage -t --long src/sage/modular/local_comp/smoothchar.py # Timed out > sage -t --long src/sage/combinat/designs/block_design.py # Timed out > sage -t --long src/sage/rings/function_field/function_field_valuation.py > # Timed out > sage -t --long src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx # > Timed out > sage -t --long src/sage/schemes/elliptic_curves/ell_torsion.py # Timed out > sage -t --long src/sage/combinat/sf/orthotriang.py # Killed due to > segmentation fault > sage -t --long src/sage/modular/modform/tests.py # Killed due to > segmentation fault > sage -t --long src/sage/schemes/curves/constructor.py # Killed due to > segmentation fault > sage -t --long src/sage/combinat/sf/powersum.py # Killed due to > segmentation fault > sage -t --long src/sage/matrix/matrix_cyclo_dense.pyx # Timed out > sage -t --long src/sage/schemes/affine/affine_morphism.py # Timed out > sage -t --long src/sage/quivers/homspace.py # Killed due to segmentation > fault > sage -t --long src/sage/rings/finite_rings/finite_field_prime_modn.py # > Killed due to segmentation fault > sage -t --long src/sage/rings/morphism.pyx # Timed out > sage -t --long src/sage/rings/padics/relative_extension_leaves.py # Timed > out > sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed > sage -t --long src/sage/coding/reed_muller_code.py # Timed out > sage -t --long src/doc/en/constructions/elliptic_curves.rst # Timed out > sage -t --long src/doc/en/constructions/number_fields.rst # Timed out > sage -t --long src/sage/cpython/dict_del_by_value.pyx # 1 doctest failed > sage -t --long src/sage/monoids/free_abelian_monoid.py # Killed due to > segmentation fault > sage -t --long src/sage/modular/overconvergent/weightspace.py # Timed out > sage -t --long src/sage/categories/complete_discrete_valuation.py # Timed > out > sage -t --long src/sage/structure/parent.pyx # Timed out > sage -t --long src/sage/rings/ring.pyx # Timed out > sage -t --long src/sage/modular/pollack_stevens/dist.pyx # Timed out > sage -t --long src/sage/rings/padics/padic_generic_element.pyx # Timed out > -- > > > > On Saturday, January 11, 2020 at 10:48:00 AM UTC+1, Jaap Spies wrote: >> >> On a Raspberry Pi 4B with 4 GB memory, running on a Western Digital 500 >> GB SDD >> >> >> real 366m47.488s >> user 942m5.388s >> sys 72m37.278s >> Sage build/upgrade complete! >> make[1]: Leaving directory '/home/pi/Downloads/sage-9.1.beta0' >> pi@rasp4g:~/Downloads/sage-9.1.beta0 $ >> >> Still running make
[sage-release] Re: Sage 9.1.beta0 released
On Debian testing running on core i7 + 16 GB RAM, upgrading a Python 3-based Sage 9.0 to 9.1.beta0 and running ptestalllong gets 3 permanent and 5 transient failures: File Result P/T src/sage/databases/oeis.py 1 doctest failed T src/sage/plot/animate.py 7 doctests failed T src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P src/sage/tests/gap_packages.py 1 doctest failed P src/sage/misc/latex.py 1 doctest failed T src/sage/libs/glpk/error.pyx 1 doctest failed P src/sage/repl/load.py 1 doctest failed T src/sage/databases/findstat.py 8 doctests failed T All of these failures have been reported multiple times. No new failure here. HTH, Le vendredi 10 janvier 2020 17:19:30 UTC+1, Volker Braun a écrit : 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 > > > b8f53f72e8 (HEAD -> develop, tag: 9.1.beta0, trac/develop) Updated > SageMath version to 9.1.beta0 > 7140d0e7bb Trac #28389: Support constructing Singular ring with ring order > with 'c' or 'C' > 1f04f40d45 Trac #27513: Allow custom order for edges as well as vertices > for incidence matrix > 5c3676468a Trac #28950: more precise assert statements > 56ef6f028c Trac #28948: some preparation for ipython7 > d6b83409eb Trac #28947: multiplicative Abelian groups are not GAP friendly > 5762334c54 Trac #28938: remove deprecated methods in some combinatorial > Hopf algebras > ae18b5d03e Trac #28937: change some doc about python3 > ba2f949961 Trac #28935: infinite recursion in exponential of sparse > matrices > b731e8b1af Trac #28933: no longer use _cmp_ in vectors > 51e7813414 Trac #28929: HyperbolicGeodesic.plot() returns None if self is > a line and boundary=False > 2b596aad84 Trac #28927: DESTDIR support for libbraiding and libhomfly > 6bfc8ed6d0 Trac #28909: Allow overriding "when building, check that user > isn't root" for use in Docker containers with configure > --enable-build-as-root > f5c516cb00 Trac #28884: spkg-configure for R > c4ed371cdf Trac #28879: spkg-configure for GSL > 3047e9e8c3 Trac #28855: PolynomialRing random_element()s aren't always > ring elements > da593dc5f5 Trac #28688: fix buckygen for modern C/C++ > 896120d9fd Trac #27870: spkg-configure.m4 for $(BLAS) (i.e. atlas and > openblas) > 304fe834c5 Trac #25903: fix Macaulay2 output when reading input from a file > 1e5c93fadf Trac #7165: sage fails to plot a quarter circle when it should > e9db0c6dde Trac #28903: Sympy-conversion of complex numbers > 2111e0063b Trac #28899: some details in rings/polynomial/ > f8c7d3650d Trac #28848: Add methods for the lattice of subsets > 2ec94231bf Trac #28557: julia_plot sometimes does not draw the entire > julia set > c80928120c Trac #23946: Exhaust over Weil polynomials > c767179b74 Trac #28930: pyflakes fix in dynamics > 1a8f1fa3fa Trac #28926: MR39: Update Developer's guide regarding pull > requests > 16052a5aa6 Trac #28919: spkg-configure for tachyon > 1890aefa44 Trac #28914: default_mip_solver: Allow solver = a callable > ebb0d39a81 Trac #28911: Update sympy to 1.5 > 889d29cb9b Trac #28897: BipartiteGraph blindly trusts generic graphs > 082db1579a Trac #28889: HyperbolicGeodesic.angle() returns mathematically > incorrect results > 3914a955ab Trac #28883: update pkgconfig to version 1.5.1 > e8987e793c Trac #28646: Use CombinatorialPolyhedron to obtain faces of > polyhedra > 4fc6fba1e8 Trac #28311: Random failure in combinatorial_polyhedron/base.pyx > 5fa32aa9f8 Trac #28175: Move optional sage optimization backends (COIN, > CPLEX, Gurobi) to separate Cython packages to remove OptionalExtension > problems > 7afa68e7ff Trac #27953: Integral curves over finite fields: base classes > 906cf147fe Trac #27424: enumeration of minimal dominating sets > 3c293de084 Trac #26355: Degenerate Metric and Degenerate Metric Manifold > 31cb54b779 (tag: 9.0, trac/master, master) Updated SageMath version to 9.0 > > -- 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/75c3c04c-0344-4392-828f-22c5894c19ad%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
On Rasbian (see below) make ptestlong ended with: -- Total time for all tests: 28699.4 seconds cpu time: 41119.9 seconds cumulative wall time: 51721.1 seconds make: *** [Makefile:178: ptestlong] Error 21 Some or most will be transient failures? I'll check. -- sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Killed due to segmentation fault sage -t --long src/sage/modular/btquotients/pautomorphicform.py # Timed out sage -t --long src/sage/rings/finite_rings/residue_field.pyx # Timed out sage -t --long src/sage/schemes/elliptic_curves/constructor.py # Timed out sage -t --long src/sage/schemes/elliptic_curves/gal_reps.py # Timed out sage -t --long src/sage/rings/function_field/function_field.py # Timed out sage -t --long src/sage/structure/coerce_dict.pyx # 1 doctest failed sage -t --long src/sage/manifolds/differentiable/mixed_form.py # Killed due to segmentation fault sage -t --long src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py # Timed out sage -t --long src/sage/combinat/tableau.py # Killed due to segmentation fault sage -t --long src/sage/combinat/designs/database.py # Timed out sage -t --long src/sage/graphs/strongly_regular_db.pyx # Killed due to segmentation fault sage -t --long src/sage/modular/hypergeometric_motive.py # Timed out sage -t --long src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # Timed out sage -t --long src/sage/categories/pushout.py # Timed out sage -t --long src/sage/modular/btquotients/btquotient.py # Timed out sage -t --long src/sage/rings/function_field/differential.py # Killed due to segmentation fault sage -t --long src/sage/rings/valuation/valuation.py # Timed out sage -t --long src/sage/schemes/toric/sheaf/klyachko.py # Timed out sage -t --long src/sage/modular/pollack_stevens/padic_lseries.py # Timed out sage -t --long src/sage/combinat/ncsym/ncsym.py # Killed due to segmentation fault sage -t --long src/sage/misc/c3_controlled.pyx # Killed due to segmentation fault sage -t --long src/sage/modular/local_comp/smoothchar.py # Timed out sage -t --long src/sage/combinat/designs/block_design.py # Timed out sage -t --long src/sage/rings/function_field/function_field_valuation.py # Timed out sage -t --long src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx # Timed out sage -t --long src/sage/schemes/elliptic_curves/ell_torsion.py # Timed out sage -t --long src/sage/combinat/sf/orthotriang.py # Killed due to segmentation fault sage -t --long src/sage/modular/modform/tests.py # Killed due to segmentation fault sage -t --long src/sage/schemes/curves/constructor.py # Killed due to segmentation fault sage -t --long src/sage/combinat/sf/powersum.py # Killed due to segmentation fault sage -t --long src/sage/matrix/matrix_cyclo_dense.pyx # Timed out sage -t --long src/sage/schemes/affine/affine_morphism.py # Timed out sage -t --long src/sage/quivers/homspace.py # Killed due to segmentation fault sage -t --long src/sage/rings/finite_rings/finite_field_prime_modn.py # Killed due to segmentation fault sage -t --long src/sage/rings/morphism.pyx # Timed out sage -t --long src/sage/rings/padics/relative_extension_leaves.py # Timed out sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed sage -t --long src/sage/coding/reed_muller_code.py # Timed out sage -t --long src/doc/en/constructions/elliptic_curves.rst # Timed out sage -t --long src/doc/en/constructions/number_fields.rst # Timed out sage -t --long src/sage/cpython/dict_del_by_value.pyx # 1 doctest failed sage -t --long src/sage/monoids/free_abelian_monoid.py # Killed due to segmentation fault sage -t --long src/sage/modular/overconvergent/weightspace.py # Timed out sage -t --long src/sage/categories/complete_discrete_valuation.py # Timed out sage -t --long src/sage/structure/parent.pyx # Timed out sage -t --long src/sage/rings/ring.pyx # Timed out sage -t --long src/sage/modular/pollack_stevens/dist.pyx # Timed out sage -t --long src/sage/rings/padics/padic_generic_element.pyx # Timed out -- On Saturday, January 11, 2020 at 10:48:00 AM UTC+1, Jaap Spies wrote: > > On a Raspberry Pi 4B with 4 GB memory, running on a Western Digital 500 GB > SDD > > > real 366m47.488s > user 942m5.388s > sys 72m37.278s > Sage build/upgrade complete! > make[1]: Leaving directory '/home/pi/Downloads/sage-9.1.beta0' > pi@rasp4g:~/Downloads/sage-9.1.beta0 $ > > Still running make ptestlong. > > > > > On Friday, January 10, 2020 at 5:19:30 PM UTC+1, 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/download-latest.html >> >> >> b8f53f72e8 (HEAD -> develop, tag: 9.1.beta0,
[sage-release] Re: Sage 9.1.beta0 released
Thanks, fixed! On Saturday, January 11, 2020 at 4:17:14 AM UTC+1, Matthias Köppe wrote: > > On Friday, January 10, 2020 at 11:19:30 AM UTC-5, 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/download-latest.html >> >> b8f53f72e8 (HEAD -> develop, tag: 9.1.beta0, trac/develop) Updated >> SageMath version to 9.1.beta0 >> > > >> 5fa32aa9f8 Trac #28175: Move optional sage optimization backends (COIN, >> CPLEX, Gurobi) to separate Cython packages to remove OptionalExtension >> problems >> >> > Volker, the new packages from #28175 are missing on the mirrors. > > -- 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/543b7bc5-ae6e-4216-bf8c-1a33ae6dee4c%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
On Friday, January 10, 2020 at 11:19:30 AM UTC-5, 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/download-latest.html > > b8f53f72e8 (HEAD -> develop, tag: 9.1.beta0, trac/develop) Updated > SageMath version to 9.1.beta0 > > 5fa32aa9f8 Trac #28175: Move optional sage optimization backends (COIN, > CPLEX, Gurobi) to separate Cython packages to remove OptionalExtension > problems > > Volker, the new packages from #28175 are missing on the mirrors. -- 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/cf61a565-02c4-4ae4-8def-93c05f7ed4fb%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta0 released
On Fedora 31 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz real65m0,958s user406m25,271s sys 21m20,069s Sage build/upgrade complete! make[1]: Leaving directory '/home/jaap/sagemath/sage-9.1.beta0' -- > All tests passed! > -- > Total time for all tests: 2418.2 seconds >cpu time: 14436.1 seconds >cumulative wall time: 18063.5 seconds > [jaap@vrede sage-9.1.beta0]$ > > -- 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/e1f40624-d9d1-486d-a630-3013d3b6671e%40googlegroups.com.
