I don't think I've seen this failure before:
sage -t --long --random-seed=214696321465302976857414484526305325295
src/sage/plot/plot3d/tachyon.py
**
File "src/sage/plot/plot3d/tachyon.py", line 126, in
sage.plot.plot3d.tachyon
After running `make configure`, the git repository is not clean:
% git status
On branch develop
Your branch is up to date with 'upstream/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
pkgs/sagemath-categories/requirements-editable.txt
And on two OS X Apple Silicon machines running Sonoma 14.4.1, new Xcode
command line tools, sagelib fails to build, as reported here:
https://groups.google.com/g/sage-support/c/05DARjR8PFI/m/ZqCuYjhIAAAJ
On Tuesday, March 26, 2024 at 5:20:02 PM UTC-7 John H Palmieri wrote:
> OS X In
OS X Intel machine, documentation fails to build with errors like
OSError: [Errno 24] Too many open files:
'/var/folders/z6/yjw_7s357yx3_mhh81__lplcgn/T/tmpu490zz15'
I just built 10.3.rc4 on the same machine and it succeeded.
On Monday, March 25, 2024 at 5:13:42 PM UTC-7 Volker Braun
Wednesday, February 28, 2024 at 2:16:42 PM UTC-8 John H Palmieri wrote:
> OS X, Apple Silicon, with many homebrew packages, including a recently
> upgraded openjpeg (from 2.5.0 to 2.5.1): pillow is failing to build, with
> the error message
>
> src/libImaging/Jpeg2KDecode
OS X, Apple Silicon, with many homebrew packages, including a recently
upgraded openjpeg (from 2.5.0 to 2.5.1): pillow is failing to build, with
the error message
src/libImaging/Jpeg2KDecode.c:673:43: error: too few arguments to
function call, expected 3, have 2
re_term_title()
File
"/Users/palmieri/Sage/TESTING/sage-10.3.beta2/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/IPython/utils/terminal.py",
line 83, in _restore_term_title_xterm
assert _xterm_term_title_saved
AssertionError
Something seems to be pretty broken.
uot;,
line 83, in _restore_term_title_xterm
assert _xterm_term_title_saved
AssertionError
The same happens if I execute several commands between the alarm and exit().
On Friday, December 15, 2023 at 7:07:53 AM UTC-8 Dima Pasechnik wrote:
> On Thursday, December 14, 2023 at 4:05:31 P
I'm using Venture 13.6.3 on one machine, Sonoma 14.2 on the other, plus a
lot of homebrew packages.
On Thursday, December 14, 2023 at 1:05:44 PM UTC-8 david@gmail.com
wrote:
> I don’t see these errors on Apple M1 with macOS 12.7.1.
>
> Le 14 déc. 2023 à 17:05, John H Palmieri
On OS X (both Intel and Apple Silicon) I'm getting a lot of new failures,
many of the form "Killed due to alarm":
sage -t --long --random-seed=144845266083009760424007645487960076680
src/sage/libs/flint/nmod_poly_linkage.pxi # Killed due to alarm
sage -t --long
Builds fine for me on OS X, both Intel and Apple Silicon. No new doctest
failures.
On Tuesday, December 5, 2023 at 4:26:09 PM UTC-8 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
>
A better link for the 3rd and 4th failures is #36631
(https://github.com/sagemath/sage/issues/36631).
On Saturday, November 11, 2023 at 9:52:26 AM UTC-8 John H Palmieri wrote:
> On OS X Intel, looks good. Four doctest failures, all of which have been
> reported:
>
> sage -t --l
Same on OS X Apple M2 chip. In both this and the earlier case, I ran
`./configure` — no need to do `./configure --with-system-gfortran=no`.
On Saturday, November 11, 2023 at 9:52:26 AM UTC-8 John H Palmieri wrote:
> On OS X Intel, looks good. Four doctest failures, all of which have b
On OS X Intel, looks good. Four doctest failures, all of which have been
reported:
sage -t --long --random-seed=120467112235779717922036180522489127126
src/sage/libs/giac/__init__.py # Timed out
sage -t --long --random-seed=120467112235779717922036180522489127126
On OS X, 10.2.rc0 behaves similarly to the previous release, no new doctest
failures.
On Sunday, November 5, 2023 at 1:18:52 PM UTC-8 John H Palmieri wrote:
> It would be great if #36599 could be merged in the 10.2 cycle: this should
> allow scipy to build with recent versions o
It would be great if #36599 could be merged in the 10.2 cycle: this should
allow scipy to build with recent versions of OS X + command-line tools,
without having to build our own gfortran. (It also silences some warnings
and therefore avoids some doctest failures.)
On Sunday, November 5, 2023
I'm seeing one new failure on two different OS X machines (one Intel, one
M2):
File
"src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py",
line 398, in
sage.tests.books.computational-mathematics-with-sagemath.mpoly_doctest
Failed example:
w
>
> On Tuesday, October 31, 2023 at 6:29:38 PM UTC+1 John H Palmieri wrote:
>
>> I don't see this yet on any mirrors.
>>
>> On Monday, October 30, 2023 at 5:22:19 PM UTC-7 Volker Braun wrote:
>>
>>> As always, you can get the latest beta version f
I don't see this yet on any mirrors.
On Monday, October 30, 2023 at 5:22:19 PM UTC-7 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
>
>
On Monday, October 9, 2023 at 2:53:57 PM UTC-7 Dima Pasechnik wrote:
On Mon, Oct 9, 2023 at 10:44 PM John H Palmieri
wrote:
>
>
>
> On Monday, October 9, 2023 at 9:44:02 AM UTC-7 Dima Pasechnik wrote:
>
> On Mon, Oct 9, 2023 at 5:39 PM John H Palmieri
wrote:
> &g
On Monday, October 9, 2023 at 9:44:02 AM UTC-7 Dima Pasechnik wrote:
On Mon, Oct 9, 2023 at 5:39 PM John H Palmieri wrote:
>
> (I tried to send this last night and I see some indication that the
message was deleted, so I'm reposting. Apologies if this has already
appeared.)
>
Or as was suggested already, "make -k" to make as many packages as
possible, and repeat until done.
On Monday, October 9, 2023 at 9:37:49 AM UTC-7 Dima Pasechnik wrote:
> well, I'm sure it's the same story, same fix:
>
> make hatch-fancy-pypi-readme
>
>
> On Mon, 9 Oct 2023, 17:25 Emmanuel
(I tried to send this last night and I see some indication that the message
was deleted, so I'm reposting. Apologies if this has already appeared.)
I see some error message (aside from those already reported) but the build
completes anyway. These are probably not new.
In pythran's log:
ERROR:
I see some error message (aside from those already reported) but the build
completes anyway. These are probably not new.
In pythran's log:
ERROR: Could not find a version that satisfies the requirement numpy (from
pythran) (from versions: none)
ERROR: No matching distribution found for numpy
several doc test failed….
>
> 28/09/2023 23:30、John H Palmieri のメール:
>
> As with the past few releases — and I think this is due to OS X and
> command-line tool upgrades, not Sage — I have been getting a number of
> failures due to some warning messages.
As with the past few releases — and I think this is due to OS X and
command-line tool upgrades, not Sage — I have been getting a number of
failures due to some warning messages. These continue with 10.2.beta5, and
they are addressed by https://github.com/sagemath/sage/pull/36337. The
Kenji: for me with updated homebrew etc., I can only get scipy to build if
I configure Sage with `./configure --with-system-gfortran=no`.
On Thursday, September 28, 2023 at 3:49:04 AM UTC-7 Kenji Iohara wrote:
> On my Mac OS 13.6 with Intel Core i5, with updated homebrew and Xcode 15,
> Python
I opened up https://github.com/sagemath/sage/pull/36337 for these ld
warnings, in case anyone else runs into the same problems.
On Monday, September 25, 2023 at 12:05:38 PM UTC-7 John H Palmieri wrote:
> I'm see these warning messages cause doctests to fail:
>
> ld: warning:
I'm see these warning messages cause doctests to fail:
ld: warning: duplicate -rpath
'/Users/jpalmier/Desktop/Sage/TESTING/sage-10.2.beta4/local/lib' ignored
and
ld: warning: ignoring duplicate libraries: '-lpari'
Should we bypass them in doctest/parsing.py, the way we have in the
om the system (homebrew
> in your case).
> Make sure they are up to date, and you don't have these packages installed
> in Sage.
> And run ./configure
>
> Perhaps the whole homebrew must be reinstated after an OS update, too.
>
> On Sun, 24 Sept 2023, 03:07 John H Palmieri,
ppropriate file to convince Sage that scipy had built, and the rest of
the build succeeded, except for some extra warnings during doctests: "ld:
warning: duplicate -rpath [...SAGE_ROOT/local/lib...] ignored"
On Saturday, September 23, 2023 at 3:59:40 PM UTC-7 John H Palmieri wrote:
>
n the M2 machine, Sage's scipy built
back in August with earlier versions of the OS (probably 13.5.2) and
command-line tools and gfortran (13.1.0).
On Saturday, September 23, 2023 at 3:34:29 PM UTC-7 Dima Pasechnik wrote:
> do they even support gcc/gfortran 13?
>
> On Sat, 23 S
Same result if I do `pip3 install scipy --no-binary scipy` (another of
their suggested ways of building from source). I guess something is broken
with my fortran compiler, but I don't know how to troubleshoot it.
On Saturday, September 23, 2023 at 2:35:52 PM UTC-7 John H Palmieri wrote
ather from scipy bug tracker,
> they can build on M2 just fine
> https://github.com/scipy/scipy/issues/18308
>
>
> On Sat, 23 Sept 2023, 18:07 John H Palmieri, wrote:
>
>> This is with an Apple Silicon laptop, M2 chip, in case that matters.
>>
>> On Saturday, Se
This is with an Apple Silicon laptop, M2 chip, in case that matters.
On Saturday, September 23, 2023 at 10:06:36 AM UTC-7 John H Palmieri wrote:
> I tried the venv approach in the scipy docs, and I ran into the same error.
>
> On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima
I tried the venv approach in the scipy docs, and I ran into the same error.
On Saturday, September 23, 2023 at 1:31:34 AM UTC-7 Dima Pasechnik wrote:
> Can you build scipy from source using their instructions?
>
> On Sat, 23 Sept 2023, 06:25 John H Palmieri, wrote:
>
>> It's f
in Sage
>
>
> On Fri, 22 Sept 2023, 00:52 John H Palmieri, wrote:
>
>> A new problem, after upgrading to OS X 13.6 and the newest version of the
>> command-line tools: scipy fails to build again, this time with the error:
>>
>> ../../meson.build:82:0: ERROR:
sonpy-".
On Thursday, September 21, 2023 at 4:52:56 PM UTC-7 John H Palmieri wrote:
> A new problem, after upgrading to OS X 13.6 and the newest version of the
> command-line tools: scipy fails to build again, this time with the error:
>
> ../../meson.build:82:0: ERROR: U
Suggestions?
On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 John H Palmieri wrote:
> Similar problem for me on OS X. I don't understand something: the
> dependencies for scipy include meson_python, but that package is not
> installed before scipy attempts to build, and fails. Runn
Similar problem for me on OS X. I don't understand something: the
dependencies for scipy include meson_python, but that package is not
installed before scipy attempts to build, and fails. Running "make
meson_python" and then "make scipy" succeeds, as does "make".
On Saturday, September 16,
That helped, thank you.
On Monday, September 11, 2023 at 8:36:29 AM UTC-7 Gonzalo Tornaría wrote:
> Please try: https://github.com/sagemath/sage/pull/36235
>
> On Monday, September 11, 2023 at 2:59:12 AM UTC-3 John H Palmieri wrote:
>
>> And now I see a similar failure with 10
And now I see a similar failure with 10.2.beta1. It could be the latest OS
X upgrade.
On Sunday, September 10, 2023 at 10:29:32 PM UTC-7 John H Palmieri wrote:
> The Sage library doesn't build for me on two OS X 13.5.2 (+ homebrew)
> machines. The tail end of the log:
>
>
The Sage library doesn't build for me on two OS X 13.5.2 (+ homebrew)
machines. The tail end of the log:
building 'sage.libs.ecl' extension
INFO: C compiler: gcc -Wsign-compare -Wunreachable-code -fno-common
-dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot
On OS X, if I run `./configure && make ptestlong`, I now only see one or
two doctest failures (old ones):
sage -t --long --random-seed=131365868289497726973344316901453636879
src/sage/rings/polynomial/multi_polynomial_ideal.py # Killed due to
segmentation fault
sage -t --long
Looks like it's skipping the files with tags at the top like
# sage.doctest: optional - sage.rings.finite_rings
That is: cardinality.py, ell_number_field.py, heegner.py, hom_frobenius.py,
isogeny_class.py, saturation.py. When I run `./sage -t
src/sage/schemes/elliptic_curves/`, it says
I think this should be discussed at sage-devel.
On Wednesday, June 28, 2023 at 8:49:51 AM UTC-7 vdelecroix wrote:
> I agree with Marc that svg is almost always preferable than png for
> graphics : it scales and compresses. Thanks for raising the issue.
>
> Do you have a concrete proposal for
> shouldn't be there
>
> On Sunday, May 28, 2023 at 10:10:23 PM UTC+2 John H Palmieri wrote:
>
>> On OS X: after running `./configure`, I see
>>
>> % git status
>> On branch develop
>> Your branch is up to date with 'upstream/develop'.
>>
&
On OS X: after running `./configure`, I see
% git status
On branch develop
Your branch is up to date with 'upstream/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
stdin.info
nothing added to commit but untracked files present (use "git add" to track)
On
There was a problem with Singular, but that should have been fixed in
#34851, merged into 10.0.beta0 in February.
(https://github.com/sagemath/sage/issues/34851)
On Tuesday, May 23, 2023 at 1:11:50 PM UTC-7 matthia...@gmail.com wrote:
> On Monday, May 22, 2023 at 11:39:09 PM UTC-7 tdumont
Thank you, Guillermo. I should have said: I'm using OS X 13.3.1 on both
machines where I'm seeing these failures. I created
https://github.com/sagemath/sage/issues/35646 for this.
On Tuesday, May 16, 2023 at 3:35:15 PM UTC-7 list...@gmail.com wrote:
>
> This is on Apple Silicon Macs ("M"
I see the same failures on a laptop with an M2 chip.
On Tuesday, May 16, 2023 at 12:58:56 PM UTC-7 John H Palmieri wrote:
> On an iMac Pro (some Intel chip), the first failure
> (rings/polynomial/multi_polynomial_ideal.py) is also related to giac:
>
> sage: A9=PolynomialRing(QQ,9,
# line 17 ##
sage: B = gb_giac(I.gens()) # random ## line 18 ##
On Monday, May 15, 2023 at 6:05:25 PM UTC-7 Kwankyu Lee wrote:
> On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote:
>
> I consistently see these failures on various OS X machines:
>
I consistently see these failures on various OS X machines:
sage -t --long --random-seed=244618093388694547212515065258622925284
src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed
sage -t --long --random-seed=244618093388694547212515065258622925284
Thank you for the reference.
On Tuesday, March 14, 2023 at 3:25:16 PM UTC-7 list...@gmail.com wrote:
>
> This is mentioned here:
> https://github.com/sagemath/sage/issues/35273
>
> Guillermo
>
> On Tue, 14 Mar 2023 at 23:09, John H Palmieri wrote:
>
>> OS X wi
OS X with homebrew packages installed and very recently updated. I'm seeing
some doctest failures: errors with mathematically equivalent answers but
not in the correct form. This is for the following files:
sage -t --long --random-seed=247900869917442955840282482235981848821
It looks like the graph failures have been reported at
https://github.com/sagemath/sage/issues/35157. Emanuel, are those the ones
you're seeing?
On Sunday, March 5, 2023 at 8:20:30 AM UTC-8 emanuel.c...@gmail.com wrote:
> The resulting 10.0.beta3 passes ptestlong witrh the two permanent
>
Some people have had an issue with Singular: the system version is too new.
Using "./configure --with-system-singular=no" (probably after "make
distclean"?) would help, if that's the problem. There is an upgrade ticket
for Singular that has had many isses, but last time I checked, it had a
Patch available: https://trac.sagemath.org/ticket/34935
On Tuesday, January 24, 2023 at 2:47:15 PM UTC-8 John H Palmieri wrote:
> I think Matthias found the answer in the emacs-lisp code (discussion at
> https://trac.sagemath.org/ticket/34547#comment:56).
>
> On Tuesday, January 2
effort to
> understand and *comment* it might be worthwile…
>
> Le mardi 24 janvier 2023 à 23:15:40 UTC+1, John H Palmieri a écrit :
>
>> For reasons I really don't understand, removing these lines from
>> sage.interfaces.all seem to have caused this:
>>
>> -interf
ry 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>
>> This was one of my guesses because that ticket could have changed global
>> behavior of Sage by changing some imports — most of the tickets made more
>> focused changes. Can you start with 9.8.beta6 and just apply some of
4 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>>> Thank you for this suggestion! I will try with 9.8.beta6 + #33842. I
>>> hope that all dependencies are in the branch.
>>>
>>> Martin
>>>
>>> On Monday, 23 January 2023 at 21:32:
sue indeed. But losing the Emacs interface
>>> is a big hit for me, so I revert to 9.6.beta6 for now.
>>>
>>> Thank you nevertheless !
>>>
>>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>>>
>>>> In the hope
In the hopes that this will fix it, I opened
https://trac.sagemath.org/ticket/34927.
On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
> Does this change fix the fricas.py failure?
>
> diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.p
Does this change fix the fricas.py failure?
diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.py
index dc2ce71f26..ceba6f90dc 100644
--- a/src/sage/interfaces/fricas.py
+++ b/src/sage/interfaces/fricas.py
@@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
"""
If you have installed Singular via homebrew, it may be too new for Sage to
handle properly. Try "./configure --with-system-singular=no". (I think this
would be fixed by https://trac.sagemath.org/ticket/34851.)
--
John
On Friday, January 20, 2023 at 7:24:52 AM UTC-8 david@gmail.com wrote:
parallel docbuilding code...)
>
> On Thu, Dec 22, 2022 at 6:06 AM John H Palmieri
> wrote:
> >
> > And it would be great if we could fix it, but I don't know what the
> problem is. I've seen it on both Apple Silicon and on Apple Intel. On the
> Intel machine, when runn
December 21, 2022 at 9:37:48 PM UTC-8 John H Palmieri wrote:
> I've seen this before, and I haven't been able to figure out what triggers
> it. It seems random: try "make doc-clean doc-uninstall && make" and it
> might succeed after a few attempts.
>
> On We
I've seen this before, and I haven't been able to figure out what triggers
it. It seems random: try "make doc-clean doc-uninstall && make" and it
might succeed after a few attempts.
On Wednesday, December 21, 2022 at 3:13:10 PM UTC-8 list...@gmail.com wrote:
>
> Help needed.
>
> This is on
, November 22, 2022 at 7:36:28 PM UTC-8 Kenji Iohara wrote:
>
>> With my Mac OS 13.0.1, with Intel Core i5, and several packages with
>> Homebrew, I have a problem with downloading
>>
>>
>> * package: numpy-1.23.5
>> last build time: Nov 23 04:33
&
th.org/ticket/34658, please test
>
>
> On Tuesday, November 22, 2022 at 10:34:52 AM UTC-8 John H Palmieri wrote:
>
>> scipy fails to build for me (OS X 13.0.1, Intel, with various homebrew
>> packages, Sage built from a new tarball):
>>
>> Successfu
scipy fails to build for me (OS X 13.0.1, Intel, with various homebrew
packages, Sage built from a new tarball):
Successfully built scipy
WARNING: Skipping scipy as it is not installed.
Using pip 22.3 from
Please check whether https://trac.sagemath.org/ticket/34741 fixes the
problem.
On Saturday, November 5, 2022 at 2:47:41 PM UTC-7 Kenji Iohara wrote:
> It might be better adding test.log
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To
Are these failures because of warning messages like
ld: warning: dylib (...) was built for newer macOS version (13.0) than
being linked (12.3)
On Friday, November 4, 2022 at 5:08:27 AM UTC-7 Kenji Iohara wrote:
> I have recompiled it with Mac OS 13.0, with Intel Core i5, Xcode 14.1 with
I added #34594 and a new ticket, #34595 (findstat internet errors) to
#25536.
On Tuesday, September 27, 2022 at 2:16:48 PM UTC-7 John H Palmieri wrote:
> I just posted a fix for the sage.misc.latex issue in
> https://trac.sagemath.org/ticket/34594.
>
> The octave issues are str
I just posted a fix for the sage.misc.latex issue in
https://trac.sagemath.org/ticket/34594.
The octave issues are strange — maybe they depend on the version of Octave?
You had posted at #33093 that you were getting this failure:
File "src/sage/interfaces/octave.py", line 158, in
Al tests pass for me on OS X Intel.
On Saturday, September 17, 2022 at 4:04:43 AM UTC-7 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
>
I opened https://trac.sagemath.org/ticket/34533 for this.
On Tuesday, September 13, 2022 at 6:44:55 PM UTC-7 John H Palmieri wrote:
> Thank you for the confirmation. I now see it on two OS X machines, one
> Intel, one Apple Silicon.
>
>
> On Tuesday, September 13, 2022 at 6:27:5
---
> (see https://trac.sagemath.org/ticket/33212).
>
> Guillermo
>
> On Wed, 14 Sept 2022 at 00:03, John H Palmieri
> wrote:
>
>> I just upgraded to OS X 12.6, with an accompanying change to Xcode. I am
>> seeing this warning when docte
I just upgraded to OS X 12.6, with an accompanying change to Xcode. I am
seeing this warning when doctesting:
sage -t --random-seed=7664506257818559554244400680707390
src/sage/misc/sagedoc.py
**
File
I just tried this, and I didn't see the same thing. After building
`dot2tex`, it ran `./configure` and then rebuilt `sage-conf` and `sagelib`;
the whole thing took about a minute.
On Tuesday, September 6, 2022 at 10:52:11 PM UTC-7 tsc...@ucdavis.edu wrote:
> I just did a build from scratch
At the start of sagemath_doc_html-none.log, I see
.../sage-9.7.rc0/src/sage/functions/special.py:852: DeprecationWarning:
invalid escape sequence '\p'
Fix is up at https://trac.sagemath.org/ticket/34465.
On Tuesday, August 30, 2022 at 6:15:10 PM UTC-7 Volker Braun wrote:
> As always, you can
Try "make doc-clean doc-uninstall", not just "make doc-clean".
On Friday, June 24, 2022 at 3:21:39 AM UTC-7 Dima Pasechnik wrote:
> On Fri, Jun 24, 2022 at 10:05 AM 'tsc...@ucdavis.edu' via sage-release
> wrote:
> >
> >
> >> Is anyone else seeing docbuilding issues? I am getting
> >>
> >>
Could this be related to https://trac.sagemath.org/ticket/33877? What
version of `giac` are you using?
On Monday, May 30, 2022 at 3:38:54 PM UTC-7 jus...@mac.com wrote:
>
>
> > On May 27, 2022, at 12:32 , Volker Braun wrote:
> >
> > As always, you can get the latest beta version from the
All tests pass, but the git status is not clean after building:
% git status
On branch develop
Your branch is up to date with 'trac/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
src/doc/en/reference/documentation/sage_docbuild/
On Friday, May 27,
Quick work, thanks!
On Wednesday, April 6, 2022 at 12:33:08 PM UTC-7 arojas wrote:
> https://trac.sagemath.org/ticket/33647
>
> El miércoles, 6 de abril de 2022 a las 21:23:05 UTC+2, John H Palmieri
> escribió:
>
>> I'm getting a doctest failure (OS X, iMac Pro):
>&g
I'm getting a doctest failure (OS X, iMac Pro):
sage -t --random-seed=282087015394155253226119703033530733169
src/sage/libs/pari/tests.py
**
File "src/sage/libs/pari/tests.py", line 786, in sage.libs.pari.tests
Failed example:
I don't see it at any of the mirrors yet...
On Sunday, March 27, 2022 at 11:03:35 AM UTC-7 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
vid.
>
> Le 5 janv. 2022 à 05:10, John H Palmieri a écrit :
>
> I am having intermittent problems building Sage on OS X from a fresh
> tarball: it's worked sometimes, failed others. When it fails, it seems to
> be because there is no script "sage" in venv/bin. (There ma
I am having intermittent problems building Sage on OS X from a fresh
tarball: it's worked sometimes, failed others. When it fails, it seems to
be because there is no script "sage" in venv/bin. (There may be other
problems, too, but this one is a major symptom.) I think this is the
pattern: if
Sorry to resurrect this old thread, but I'm seeing the same numerical
doctest failures on an OS X machine with Sage 9.5.beta1. Any ideas where
these could be coming from? Some miscompiled component coming from the
system, or something from within Sage itself? I started seeing these after
After seeing the message "Pytest is not installed, skip checking tests that
rely on it" a number of times, I decided to install it. There were two
files with resulting doctest failures:
sage -t --long --warn-long 131.5 --random-seed=0 src/sage/doctest/test.py
# 7 doctests failed
sage -t
It builds for me on OS X Big Sur and I see no new doctest failures, but the
PDF documentation doesn't build. When building it/a_tour_of_sage, I see
this error:
! Package inputenc Error: Unicode character リ (U+30EA)
Indeed, the file
I just noticed something which has been happening for all of the 9.3 beta
releases, maybe before that. In the dochtml.log file, I see the message
Help file /Applications/usr/share/giac/doc/fr/aide_cas not found
(This is on OS X.) That's a strange path — there is no /Applications/usr —
so
h an
error that I don't know how to fix, as reported at
https://trac.sagemath.org/ticket/30651.
On Monday, December 28, 2020 at 11:10:36 AM UTC-8 John H Palmieri wrote:
> I've been having problems with computers running Mac OS for several Sage
> releases now. With OS X 10.15.7
I've been having problems with computers running Mac OS for several Sage
releases now. With OS X 10.15.7 and a pretty full homebrew installation,
cypari fails:
cypari2/gen.c:23742:70: error: too many arguments to function call,
expected 3, have 4
__pyx_v__ret = asympnum0(__pyx_v__expr,
Dima is suggesting the command locale.setlocale(locale.LC_ALL,''), where
just before the parenthesis should be two single quotes. No quotes after
the parenthesis. Or if you prefer: locale.setlocale(locale.LC_ALL,"") with
two double quotes just before the parenthesis.
On Thursday, November 26,
On Monday, November 2, 2020 at 1:38:37 PM UTC-8, Dima Pasechnik wrote:
>
>
>
> On Mon, 2 Nov 2020, 21:36 David Coudert, > wrote:
>
>> So should we open a ticket to add it and hope it will be included in next
>> beta or is there a trick to force the installation of giac ?
>>
>
"make giac"
On Sunday, November 1, 2020 at 7:29:31 AM UTC-8, David Coudert wrote:
>
> Hello,
>
> I’m unable to build beta0 on macOS 10.15.7 :(
>
> I did:
> $ make distclean
> $ ./bootstrap
> $ source .homebrew-build-env
> $ ./configure
>
> Then, I followed the recommandation and did:
> $ brew install pandoc
Please also provide the top-level config.log.
On Thursday, October 1, 2020 at 5:11:01 AM UTC-7, Kenji Iohara wrote:
>
> On OS X.15.7 with Xcode 12, I couldn’t compile
>
>pynac-0.7.26.sage-2020-04-03.p0
>
> . Here is its log-file.
>
--
You received this message because you are
Builds for me on OS X 10.15.7 (Catalina) with Xcode 12, both with a full
homebrew installation, and then also using only some homebrew packages:
./configure --with-system-readline=no --with-system-openblas=no
--with-system-r=no --with-system-gsl-no --with-system-suitesparse=no
On
1 - 100 of 232 matches
Mail list logo
