[sage-release] Re: Sage 9.1.beta9 released
On Tuesday, March 31, 2020 at 6:21:42 PM UTC-7, Matthias Köppe wrote: > > On Tuesday, March 31, 2020 at 8:02:48 PM UTC-4, John H Palmieri wrote: >> >> Here's the strange part: if I add the package libpng, then Sage doesn't >> build. With these packages, it builds and passes tests (output from "brew >> list --versions"): >> >> autoconf 2.69 >> automake 1.16.2 >> boost 1.72.0_1 >> cabextract 1.9.1 >> emacs-mac emacs-26.3-z-mac-7.9 >> gcc 9.2.0_1 9.3.0 >> gdbm 1.18.1 >> gettext 0.20.1 >> gmp 6.2.0 6.1.2_2 >> gnutls 3.6.12 >> icu4c 64.2 >> isl 0.22.1 0.21 0.18 >> jpeg 9d >> libdvdcss 1.4.2 >> libevent 2.1.11_1 >> libffi 3.2.1 >> libidn2 2.3.0 >> libmpc 1.1.0 >> libtasn1 4.14 4.16.0 >> libtiff 4.1.0 >> libunistring 0.9.10 >> mpfr 4.0.2 >> nettle 3.4.1 >> openssl@1.1 1.1.1d >> p11-kit 0.23.20 0.23.18.1 >> pkg-config 0.29.2 >> readline 8.0.4 >> sqlite 3.31.1 >> unbound 1.9.4 1.10.0 >> xz 5.2.5 >> > > python3's spkg-configure refuses to use system python if we install any of > the following from spkg: > > sqlite libpng bzip2 xz libffi > > bzip2 comes from /usr/bin > The others from homebrew. > When you install libpng in addition to the list of packages, the set of > prerequisites for accepting system python3 is complete, and then the > unresolved problems with the build (kiwisolver, ...) appear when system > python 3 is /usr/bin/python3 (XCode's python3). > > It does not happen if you have homebrew python3 in PATH. > Right, I realized that, too. However, I initially had even more homebrew packages installed, Sage built using the system Python, and the build succeeded. That's when I ran into the doctest failures, which I am now trying to reproduce: trying to see which homebrew packages trigger them. -- 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/5b95f224-4556-442e-9543-6e9f65eb8cfc%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
On Tuesday, March 31, 2020 at 8:02:48 PM UTC-4, John H Palmieri wrote: > > Here's the strange part: if I add the package libpng, then Sage doesn't > build. With these packages, it builds and passes tests (output from "brew > list --versions"): > > autoconf 2.69 > automake 1.16.2 > boost 1.72.0_1 > cabextract 1.9.1 > emacs-mac emacs-26.3-z-mac-7.9 > gcc 9.2.0_1 9.3.0 > gdbm 1.18.1 > gettext 0.20.1 > gmp 6.2.0 6.1.2_2 > gnutls 3.6.12 > icu4c 64.2 > isl 0.22.1 0.21 0.18 > jpeg 9d > libdvdcss 1.4.2 > libevent 2.1.11_1 > libffi 3.2.1 > libidn2 2.3.0 > libmpc 1.1.0 > libtasn1 4.14 4.16.0 > libtiff 4.1.0 > libunistring 0.9.10 > mpfr 4.0.2 > nettle 3.4.1 > openssl@1.1 1.1.1d > p11-kit 0.23.20 0.23.18.1 > pkg-config 0.29.2 > readline 8.0.4 > sqlite 3.31.1 > unbound 1.9.4 1.10.0 > xz 5.2.5 > python3's spkg-configure refuses to use system python if we install any of the following from spkg: sqlite libpng bzip2 xz libffi bzip2 comes from /usr/bin The others from homebrew. When you install libpng in addition to the list of packages, the set of prerequisites for accepting system python3 is complete, and then the unresolved problems with the build (kiwisolver, ...) appear when system python 3 is /usr/bin/python3 (XCode's python3). It does not happen if you have homebrew python3 in PATH. -- 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/58bf8274-c59a-4659-bdfc-963f1250614d%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
On Tuesday, March 31, 2020 at 8:02:48 PM UTC-4, John H Palmieri wrote: > > [...] > kiwisolver fails to build. For some reason, something in the build process > thinks that "-sdk" is a good flag to add to "g++": > > g++ -sdk macosx clang -bundle -undefined dynamic_lookup > -L/Users/palmieri/Desktop/Sage_stuff/sage_builds/TESTING/png/sage-9.1.beta9/local/lib > > -Wl,-rpath,/Users/palmieri/Desktop/Sage_stuff/sage_builds/TESTING/png/sage-9.1.beta9/local/lib > > build/temp.macosx-10.14-x86_64-3.7/py/kiwisolver.o > build/temp.macosx-10.14-x86_64-3.7/py/constraint.o > build/temp.macosx-10.14-x86_64-3.7/py/expression.o > build/temp.macosx-10.14-x86_64-3.7/py/solver.o > build/temp.macosx-10.14-x86_64-3.7/py/strength.o > build/temp.macosx-10.14-x86_64-3.7/py/term.o > build/temp.macosx-10.14-x86_64-3.7/py/variable.o -o > build/lib.macosx-10.14-x86_64-3.7/kiwisolver.cpython-37m-darwin.so > clang: error: unknown argument: '-sdk' > clang: error: no such file or directory: 'macosx' > clang: error: no such file or directory: 'clang' > error: command 'g++' failed with exit status 1 > > I didn't see this before, so if I add enough other packages, this problem > will somehow resolve itself. This is specific to 9.1.beta9 (i.e., using the > system python3): kiwisolver builds with 9.1.beta8 and these homebrew > packages. > This is https://trac.sagemath.org/ticket/29408 -- 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/bdf4fc8e-c205-42d6-8d60-3bc5c24b60bd%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
On Tuesday, March 31, 2020 at 4:18:08 PM UTC-4, Markus Wageringel wrote:
>
> Since this beta, I get the following permanent failure:
>
> sage -t --long src/sage/env.py
> **
> File "src/sage/env.py", line 15, in sage.env
> Failed example:
> out == repr((SAGE_ROOT, SAGE_LOCAL))
># long time
> Expected:
> True
> Got:
> False
>
> Here, SAGE_ROOT and SAGE_LOCAL look correct, but the `out` variable from
> the preceding tests is
>
> sage: env = {k:v for (k,v) in os.environ.items() if not k.startswith(
> "SAGE_")}
> sage: from subprocess import check_output
> sage: cmd = "from sage.all import SAGE_ROOT, SAGE_LOCAL;
> print((SAGE_ROOT, SAGE_LOCAL))"
> sage: out = check_output([sys.executable, "-c", cmd], env=env).decode
> ().strip() # long time
> sage: out
> "('/home/math/sagebot/sage', '/amd/compute/sagebot/sage/local')"
>
> The left path is actually a symlink in my home directory to my sage root
> directory on a different partition:
>
> sage: SAGE_ROOT
> '/amd/compute/sagebot/sage'
>
>
>
Looks like this new doctest (from https://trac.sagemath.org/ticket/29287)
needs some os.path.abspath in it. Please open a ticket for this.
--
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/76ce1503-fead-4e94-a1b9-073006645f26%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
On Tuesday, March 31, 2020 at 4:18:08 PM UTC-4, Markus Wageringel wrote: > > my patchbot failed multiple times with the following possibly related > error: > > ... > Sage build/upgrade complete! > make[1]: Verzeichnis „/amd/compute/sagebot/sage“ wird verlassen > sh: /amd/compute/sagebot/sage/local/bin/sage-starts: Datei oder > Verzeichnis nicht gefunden > > That is, the file `local/bin/sage-starts` is not found. This is with > CentOS 7.7. > > This script was moved in https://trac.sagemath.org/ticket/23769 -- 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/2751c224-bde4-4ad0-941a-4f85f09c9c04%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
Since this beta, I get the following permanent failure:
sage -t --long src/sage/env.py
**
File "src/sage/env.py", line 15, in sage.env
Failed example:
out == repr((SAGE_ROOT, SAGE_LOCAL))
# long time
Expected:
True
Got:
False
Here, SAGE_ROOT and SAGE_LOCAL look correct, but the `out` variable from
the preceding tests is
sage: env = {k:v for (k,v) in os.environ.items() if not k.startswith(
"SAGE_")}
sage: from subprocess import check_output
sage: cmd = "from sage.all import SAGE_ROOT, SAGE_LOCAL;
print((SAGE_ROOT, SAGE_LOCAL))"
sage: out = check_output([sys.executable, "-c", cmd], env=env).decode().
strip() # long time
sage: out
"('/home/math/sagebot/sage', '/amd/compute/sagebot/sage/local')"
The left path is actually a symlink in my home directory to my sage root
directory on a different partition:
sage: SAGE_ROOT
'/amd/compute/sagebot/sage'
Moreover, my patchbot failed multiple times with the following possibly
related error:
...
Sage build/upgrade complete!
make[1]: Verzeichnis „/amd/compute/sagebot/sage“ wird verlassen
sh: /amd/compute/sagebot/sage/local/bin/sage-starts: Datei oder
Verzeichnis nicht gefunden
That is, the file `local/bin/sage-starts` is not found. This is with CentOS
7.7.
--
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/d093c8bf-1fd0-4510-964b-0b7dcc88ccac%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
I also see the error in rings/integer.pyx again now. This is
https://trac.sagemath.org/ticket/28106. The doctests are limited to 3300 MB
of memory be default, but this test exceeds it. The limit can be manually
increased using the `--memlimit` option.
Am Dienstag, 31. März 2020 19:40:19 UTC+2 schrieb Steven Trogdon:
>
> I'm replying to my previous post.
>
> I rebuilt Sage using the Sage-provided python instead my system python and
> doctested Sage. The failure in doctest/test.py disappears. However, the
> failures in rings/integer.pyx still persist. I suspect a system component
> is the culprit. Any ideas which one? I had doctested 9.1.beta8 with no
> failures, so something has changed.
>
> On Monday, March 30, 2020 at 4:54:19 PM UTC-5, Steven Trogdon wrote:
>>
>> *Gentoo*
>>
>> Incremental build 9.1.beta8 -> 9.1.beta9
>>
>> After make python3-clean && make I have the following failures:
>>
>> --
>> sage -t --long --warn-long 115.0 src/sage/doctest/test.py # 1 doctest
>> failed
>> sage -t --long --warn-long 115.0 src/sage/rings/integer.pyx # 2 doctests
>> failed
>> --
>>
>> System python is 3.7.6
>>
>> The failures:
>>
>> sage -t --long --warn-long 115.0 src/sage/doctest/test.py
>> **
>> File "src/sage/doctest/test.py", line 521, in sage.doctest.test
>> Failed example:
>> if system() == "Linux":
>> P = subprocess.Popen(["sage", "-t", "--warn-long", "0",
>> "--memlimit=2000", "memlimit.rst"], stdout=subprocess.PIPE, **kwds)
>> out, err = P.communicate()
>> ok = ("MemoryError: failed to allocate" in bytes_to_str(out))
>> Expected nothing
>> Got:
>> Process DocTestWorker-1:
>> Traceback (most recent call last):
>> File "/usr/lib/python3.7/multiprocessing/process.py", line 297, in
>> _bootstrap
>> self.run()
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 2172, in run
>> task(self.options, self.outtmpfile, msgpipe, self.result_queue)
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 2525, in __call__
>> result_queue.put(result, False)
>> File "/usr/lib/python3.7/multiprocessing/queues.py", line 87, in put
>> self._start_thread()
>> File "/usr/lib/python3.7/multiprocessing/queues.py", line 170, in
>> _start_thread
>> self._thread.start()
>> File "/usr/lib/python3.7/threading.py", line 852, in start
>> _start_new_thread(self._bootstrap, ())
>> RuntimeError: can't start new thread
>> **
>>
>> sage -t --long --warn-long 115.0 src/sage/rings/integer.pyx
>> **
>> File "src/sage/rings/integer.pyx", line 3118, in
>> sage.rings.integer.Integer.divisors
>> Failed example:
>> for i in range(20): # long time
>> try:
>> alarm(RDF.random_element(1e-3, 0.5))
>> _ = n.divisors()
>> cancel_alarm() # we never get here
>> except AlarmInterrupt:
>> pass
>> Exception raised:
>> Traceback (most recent call last):
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 681, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 1123, in compile_and_execute
>> exec(compiled, globs)
>> File "", line 4,
>> in
>> _ = n.divisors()
>> File "sage/rings/integer.pyx", line 3188, in
>> sage.rings.integer.Integer.divisors
>> (build/cythonized/sage/rings/integer.c:20544)
>> ptr = check_allocarray(divisor_count, 3 *
>> sizeof(unsigned long))
>> File "memory.pxd", line 87, in cysignals.memory.check_allocarray
>> (build/cythonized/sage/rings/integer.c:46769)
>> MemoryError: failed to allocate 33554432 * 24 bytes
>> **
>> File "src/sage/rings/integer.pyx", line 3790, in
>> sage.rings.integer.Integer.trial_division
>> Failed example:
>> n = 2 * next_prime(10^40); n.trial_division()
>> Exception raised:
>> Traceback (most recent call last):
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 681, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>> File
>> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>
>> line 1123, in
[sage-release] Re: Sage 9.1.beta9 released
Testing with many 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 -- 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 # Bad exit: 14 sage -t --long src/sage/graphs/generators/smallgraphs.py # 2 doctests failed sage -t --long src/sage/plot/animate.py # 7 doctests 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, I get: -- 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 # Bad exit: 1 sage -t --long src/sage/graphs/generators/smallgraphs.py # 2 doctests failed sage -t --long src/sage/plot/animate.py # 7 doctests failed -- External software detected for doctesting: ffmpeg,imagemagick,internet These are known issues. Follow up at https://trac.sagemath.org/ticket/25536 The external.py failing test which does not reproduce is copied below. sage -t --long src/sage/symbolic/integration/external.py ** File "src/sage/symbolic/integration/external.py", line 91, in sage.symbolic.integration.external.mma_free_integrator Failed example: integral(sin(y)^2, y, algorithm='mathematica_free') # optional - internet Expected: 1/2*y - 1/4*sin(2*y) Got: -1/2*cos(y)*sin(y) + 1/2*y ** 1 item had failures: 1 of 7 in sage.symbolic.integration.external.mma_free_integrator 8 fricas tests not run 0 tests not run because we ran out of time [36 tests, 1 failure, 21.85 s] -- 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/b860c58f-aac8-4f54-b958-e739737aff13%40googlegroups.com.
[sage-release] Re: Sage 9.1.beta9 released
I'm replying to my previous post.
I rebuilt Sage using the Sage-provided python instead my system python and
doctested Sage. The failure in doctest/test.py disappears. However, the
failures in rings/integer.pyx still persist. I suspect a system component
is the culprit. Any ideas which one? I had doctested 9.1.beta8 with no
failures, so something has changed.
On Monday, March 30, 2020 at 4:54:19 PM UTC-5, Steven Trogdon wrote:
>
> *Gentoo*
>
> Incremental build 9.1.beta8 -> 9.1.beta9
>
> After make python3-clean && make I have the following failures:
>
> --
> sage -t --long --warn-long 115.0 src/sage/doctest/test.py # 1 doctest
> failed
> sage -t --long --warn-long 115.0 src/sage/rings/integer.pyx # 2 doctests
> failed
> --
>
> System python is 3.7.6
>
> The failures:
>
> sage -t --long --warn-long 115.0 src/sage/doctest/test.py
> **
> File "src/sage/doctest/test.py", line 521, in sage.doctest.test
> Failed example:
> if system() == "Linux":
> P = subprocess.Popen(["sage", "-t", "--warn-long", "0",
> "--memlimit=2000", "memlimit.rst"], stdout=subprocess.PIPE, **kwds)
> out, err = P.communicate()
> ok = ("MemoryError: failed to allocate" in bytes_to_str(out))
> Expected nothing
> Got:
> Process DocTestWorker-1:
> Traceback (most recent call last):
> File "/usr/lib/python3.7/multiprocessing/process.py", line 297, in
> _bootstrap
> self.run()
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 2172, in run
> task(self.options, self.outtmpfile, msgpipe, self.result_queue)
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 2525, in __call__
> result_queue.put(result, False)
> File "/usr/lib/python3.7/multiprocessing/queues.py", line 87, in put
> self._start_thread()
> File "/usr/lib/python3.7/multiprocessing/queues.py", line 170, in
> _start_thread
> self._thread.start()
> File "/usr/lib/python3.7/threading.py", line 852, in start
> _start_new_thread(self._bootstrap, ())
> RuntimeError: can't start new thread
> **
>
> sage -t --long --warn-long 115.0 src/sage/rings/integer.pyx
> **
> File "src/sage/rings/integer.pyx", line 3118, in
> sage.rings.integer.Integer.divisors
> Failed example:
> for i in range(20): # long time
> try:
> alarm(RDF.random_element(1e-3, 0.5))
> _ = n.divisors()
> cancel_alarm() # we never get here
> except AlarmInterrupt:
> pass
> Exception raised:
> Traceback (most recent call last):
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 681, in _run
> self.compile_and_execute(example, compiler, test.globs)
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 1123, in compile_and_execute
> exec(compiled, globs)
> File "", line 4, in
>
> _ = n.divisors()
> File "sage/rings/integer.pyx", line 3188, in
> sage.rings.integer.Integer.divisors
> (build/cythonized/sage/rings/integer.c:20544)
> ptr = check_allocarray(divisor_count, 3 *
> sizeof(unsigned long))
> File "memory.pxd", line 87, in cysignals.memory.check_allocarray
> (build/cythonized/sage/rings/integer.c:46769)
> MemoryError: failed to allocate 33554432 * 24 bytes
> **
> File "src/sage/rings/integer.pyx", line 3790, in
> sage.rings.integer.Integer.trial_division
> Failed example:
> n = 2 * next_prime(10^40); n.trial_division()
> Exception raised:
> Traceback (most recent call last):
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 681, in _run
> self.compile_and_execute(example, compiler, test.globs)
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>
> line 1123, in compile_and_execute
> exec(compiled, globs)
> File "", line
> 1, in
> n = Integer(2) * next_prime(Integer(10)**Integer(40));
> n.trial_division()
> File
> "/mnt/backup/storage/sage-git_develop/sage/local/lib/python3.7/site-packages/sage/arith/misc.py",
>
> line 1193, in next_prime
> return ZZ(n).next_prime(proof)
> File "sage/rings/integer.pyx", line 5774, in
> sage.rings.integer.Integer.next_prime
>
Re: [sage-release] Re: Sage 9.1.beta9 released
On Monday, March 30, 2020 at 3:03:14 PM UTC-4, vdelecroix wrote: > > > Le 29/03/2020 à 21:50, Matthias Köppe a écrit : > > > > Let me remark that this is the first beta that tries to use the system > > python3 in a venv (#27824) instead of building our own copy of python3. > > Tests of building from scratch or (after "make python3-clean") would be > > valuable. > > Very disappointing > > configure:25182: checking ... whether /usr/bin/python3 is good > configure:25329: result: no, Python 3.8.2 is too recent > > You can override this by: ./configure PYTHON3=/usr/bin/python3 but then you will likely run into the issues discussed on the Python 3.8 upgrade ticket (https://trac.sagemath.org/ticket/27754). Matthias -- 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/d6007725-0d8a-488d-9bc2-83c93d14c59c%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta9 released
On Tue, Mar 31, 2020 at 9:35 PM Steven Trogdon wrote: > > A feature or a bug? 'make distclean && make' always uses the system python to > build Sage. Is there some way to force building and using the Sage-supplied > python? sure, you can use ./configure -h to see how to have packages built Namely ./configure --with-system-python3=no will do this for you. -- 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/CAAWYfq2qmK7s8h%2BXys%2BLOVT54EXdhcCyCFHgQ96w2Uffxt_AFQ%40mail.gmail.com.
[sage-release] Re: Sage 9.1.beta9 released
A feature or a bug? 'make distclean && make' always uses the system python to build Sage. Is there some way to force building and using the Sage-supplied python? -- 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/72b22851-da10-4035-902f-895ae7e2dee9%40googlegroups.com.
Re: [sage-release] Re: Sage 9.1.beta9 released
On Tue, Mar 31, 2020 at 7:46 PM Simon King wrote: > > Hi all, > > On 2020-03-31, Matthias Köppe wrote: > >> > I don't know, but I found these instructions: > >> > https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa > >> > that also mention what packages should be installed > >> > >> Excellent! After installing them and doing ./configure, I see this line: > >> python3-3.7.3.p1:using system package; SPKG > >> will not be installed > >> > >> > > Great, this looks like progress. And thanks for telling me about the > > deadsnakes ppa, this may be useful at some point. > > > > > >> So, now I can try whether it works > >> > >> > > If it doesn't, please post the logs, as usual. > > It *almost* worked. On Ubuntu 16.04 with Python 3.7.7 installed from a > ppa, I get > sage -t --warn-long 44.6 src/sage/rings/padics/padic_lattice_element.py # 3 > doctests failed this is a well-known bug/feature - the authors of this code have hard time deciding whether this should remain experimental, or not... (I don't understand why on some platforms these tests fail, while on some they don't) https://trac.sagemath.org/ticket/29272 > sage -t --warn-long 44.6 src/sage/interfaces/psage.py # 1 doctest failed > > with SageMath version 9.1.beta9, Release Date: 2020-03-29. > > I posted config.log, dochtml.doc, install.log, start.log and test.log > here: https://users.fmi.uni-jena.de/~king/logs/ > > Best regards, > Simon > > -- > 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/r5vaih%24tn5%241%40ciao.gmane.io. -- 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/CAAWYfq293QVDfMQFwXH-pc_%2BmzN7P8wxz9Dw%3Don5NmS1f%3D5Lcg%40mail.gmail.com.
[sage-release] Re: Sage 9.1.beta9 released
Hi all, On 2020-03-31, Matthias Köppe wrote: >> > I don't know, but I found these instructions: >> > https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa >> > that also mention what packages should be installed >> >> Excellent! After installing them and doing ./configure, I see this line: >> python3-3.7.3.p1:using system package; SPKG >> will not be installed >> >> > Great, this looks like progress. And thanks for telling me about the > deadsnakes ppa, this may be useful at some point. > > >> So, now I can try whether it works >> >> > If it doesn't, please post the logs, as usual. It *almost* worked. On Ubuntu 16.04 with Python 3.7.7 installed from a ppa, I get sage -t --warn-long 44.6 src/sage/rings/padics/padic_lattice_element.py # 3 doctests failed sage -t --warn-long 44.6 src/sage/interfaces/psage.py # 1 doctest failed with SageMath version 9.1.beta9, Release Date: 2020-03-29. I posted config.log, dochtml.doc, install.log, start.log and test.log here: https://users.fmi.uni-jena.de/~king/logs/ Best regards, Simon -- 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/r5vaih%24tn5%241%40ciao.gmane.io.
Re: [sage-release] Sage 9.1.beta9 released
On Monday, March 30, 2020 at 11:09:06 PM UTC-4, Dima Pasechnik wrote: > > > On Tuesday, March 31, 2020 at 10:30:39 AM UTC+8, Dima Pasechnik wrote: >> >> I'm getting this silly error while installing pillow: >> >> Copying package files from temporary location >> /home/scratch2/dimpase/sage/sage/local/var/tmp/sage/build/pillow-5.3.0.p0/inst >> >> >> to /home/scratch2/dimpase/sage/sage/local >> cp: cannot overwrite non-directory >> '/home/scratch2/dimpase/sage/sage/local/./lib64' with directory >> '/home/scratch2/dimpase/sage/sage/local/var/tmp/sage/build/pillow-5.3.0.p0/inst/home/scratch2/dimpase/sage/sage/local/./lib64' >> >> >> >> Error copying files for pillow-5.3.0.p0. >> >> -- >> >> note that >> $ ls -l /home/scratch2/dimpase/sage/sage/local/./lib64 >> lrwxrwxrwx 1 dimpase staff 3 Mar 30 18:26 >> /home/scratch2/dimpase/sage/sage/local/./lib64 -> lib >> >> >> this is with system Python 3 on Fedora 30 (with Sage's built Python3 > everything works, so apparently there is a sneaked in lib64 > path that breaks things, and I don't really know how to fix this. > These sorts of errors appeared before in Sage, cf. e.g. > https://trac.sagemath.org/ticket/26996 > I worked around this for gfortran too -- but this really needs fixing in #26996. -- 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/1e4000a5-475e-45ef-9a57-ca0247780cce%40googlegroups.com.
