15.1.0) 15.1.0
>>>>> [...]
>>>>> real_configure:18788: will use system package and not install SPKG
>>>>> gfortran
>>>>>
>>>>> which really say what it is, and what's going to be used.
>>>>>
>>>
te even more mess than what's our
>>> current build system already is.
>>> A quick an dirty fix is to replace their `openblas.pc` with the
>>> corrected one, where openmp is not mentioned
>>> at all - in the same vein as done in
>>> https://github.
etter path to go forward.
>
>
>>
>>
>>
>>
>>
>> Also, maybe “yes” to being an Apple Accelerate Guinea pig. Let’s see what
>transpires…
>
>Thanks! I've just made a draft PR from the branch I mentioned
>https://github.com/sagemath/sag
The docbuilding might be fixed by
https://github.com/sagemath/sage/pull/40457
(at least I cannot reproduce any doctest building errors with this PR)
On Saturday, July 26, 2025 at 1:15:50 AM UTC-5 tdumont wrote:
> Hello,
>
> The installation process failed when upgrading documentation.
>
> - Prob
s Martinez-Garcia
wrote:
>
> Dear Dima Pasechnik,
>
> I hope this email finds you well. I am writing to you for advice. As you may
> have seen, Robbie Hanson (in CC, now at Imperial) and I have completed a
> Sagemath library to describe Geometric Invariant Theory quotients. The
Hi,
how is your Sagemath installed?
I suppose this is related to testing
https://github.com/sagemath/cypari2/pull/180 - let's discuss there.
I'm currently also trying to test this PR locally.
Dima
On Mon, Jul 14, 2025 at 7:08 AM Risan wrote:
>
> Dear sage-devel,
>
> I am attempting to test a cyp
the point is that sagemath_giac is an optional package, it is not
built/installed by default
On July 12, 2025 5:40:19 AM CDT, Georgi Guninski wrote:
>On Fri, Jul 11, 2025 at 6:32 PM Dima Pasechnik wrote:
>>
>> I reported this on their github repo sagemath/sagecell
>>
I reported this on their github repo sagemath/sagecell
They also have a dedicated Google Group, for which this would be a better place
to report
On July 11, 2025 9:07:34 AM CDT, Georgi Guninski wrote:
>FYI the following fails on 10.6 and https://sagecell.sagemath.org/
>
>print(giac.version())
>
erate Guinea pig. Let’s see what
> transpires…
Thanks! I've just made a draft PR from the branch I mentioned
https://github.com/sagemath/sage/pull/40397
Would most appreciate feedback from you and any other volunteers.
Cheers,
Dima
>
>
>
>
>
>
>
> --
>
> Aaron Lauve (h
Hi Aaron,
thanks for the report.
The email interface to google groups allows bigger attachments, by the way.
(you can also email these logs directly to me)
There could be several reasons for all this, but first of all, it's
good to understand why the Homebrew's openblas is not accepted.
Can you se
This is an Arch-specific issue
On July 9, 2025 6:36:40 PM CDT, "'Nasser M. Abbasi' via sage-devel"
wrote:
>I am on arch based system. Installed sagemath using pacman. I no longer
>build from source.
>
>Also installed giac latest using pacman. (same for Fricas and maxima)
>
>But when from insi
This is the error most probably caused by setting, as suggested in our README:
export MAKEFLAGS="-j$(nproc) -l$(nproc).5"
but your "make" does not like it.
Can you instead do something like
export MAKEFLAGS="-j8"
and try again
On Wed, Jul 9, 2025 at 11:48 AM Šarūnas Burdulis
wrote:
>
> Hi,
> Tr
Dear Stuart,
thanks for the message. We don't test Sagemath on machines with
Mathematica installed, sorry.
Do you actually have a working Mathematica installation?
Sage is able to use terminal interface to it, using "math" command.
Does typing "math" (without quotes) in the terminal give you a
Mat
yes, this is because the superduperminimal _bootstrap pre-reqs don't
have pkg-config, and pkg-config is no longer a Sage spkg, so it can't
get installed by Sage, it has to be provided. This broke some
package/wheels related CI.
Should be fixed in the coming beta.
On Fri, Jul 4, 2025 at 1:19 PM seb
OK, then it's just a straightforward rebuild
On July 3, 2025 7:27:00 PM CDT, Nils Bruin wrote:
>On Thursday, 3 July 2025 at 17:25:48 UTC-7 Nils Bruin wrote:
>
>This file /usr/lib64/libflint.so.19 does exist.
>
>
> Apologies. Does NOT exist.
>
>--
>You received this message because you are subsc
Hi Nils,
with two dylibs like this, you are basically at the mercy of the linker.
E.g. OS updates often lead to this sort of thing, and indeed you might want to
clean and rebuild all the consumers of libflint.so,
which you can see by
git grep flint build/pkgs/*/dep*
(some of these you might no
Hi Ralf,
did you try an html manual (pdf looks a bit broken)? Anyway,
that part of the manual isn't strongly worded enough at the moment. Naturally
you should have fortran on the system (gfortran - typically a part of gcc suite
of compilers)
and Python 3.11 or newer with the development compone
;>> of Y, and S_2 acts by swapping the positions in the tuples. For example:
>>>
>>> (1,2) *_H ((12), (ab), (21), (ba)) = ((21), (ba), (12), (ab), so that's a
>>> fixed point, whereas
>>> (1,2) *_H ((12), (21), (ab), (ba)) = ((21), (12), (ba), (ab) is
This README is editable for anyone on this list:
https://github.com/orgs/sagemath/teams/core?query=role%3Amaintainer
(but not for anyone else)
On Fri, May 30, 2025 at 12:23 PM Nils Bruin wrote:
>
> I noticed that sagemath's
> https://github.com/sagemath?view_as=public
> still lists "transition fr
Currently Sage has a unused for years ability to build bzip2 spkg. The
PR https://github.com/sagemath/sage/pull/40011 moves bzip2 to the
pre-reqs, where it should belong,
as it's available on all systems we support.
Thanks
Dima
--
You received this message because you are subscribed to the Googl
o compile it anyway.
>>
>> Benjamín M. Moraga
>>
>>
>> El vie, 23 may 2025 a las 13:47, Dima Pasechnik ()
>> escribió:
>>
>>> On Fri, May 23, 2025 at 11:46 AM Antonio Rojas wrote:
>>> >
>>> > Arch ships version 4.0 which
>I think, the compiler doesn't recognize de system version of planarity,
>because it tries to compile it anyway.
>
>Benjamín M. Moraga
>
>
>El vie, 23 may 2025 a las 13:47, Dima Pasechnik ()
>escribió:
>
>> On Fri, May 23, 2025 at 11:46 AM Antonio Rojas wrote:
On May 25, 2025 6:05:31 PM CDT, "Grégory Vanuxem" wrote:
>Hello,
>
>Le dim. 25 mai 2025 à 18:21, Ricardo Fodra a
>écrit :
>
>>
>> Error building package gfortran-14.2.0
>> *
Hi,
Can you rather install and use system gfortran?
HTH
Dima
On May 25, 2025 7:07:06 AM CDT, Ricardo Fodra wrote:
>
>Error building package gfortran-14.2.0
>*
As your gcc is now gcc-15, supporting it is work in progress.
Hopefully complete by the time Sage 10.7 is out. (there are many fixes
merged in the current beta, but not all, still)
On Fri, May 23, 2025, 17:22 Richard Quint wrote:
> I am unable to build sage-10.6 from source on a PC running Ubun
On Fri, May 23, 2025 at 11:46 AM Antonio Rojas wrote:
>
> Arch ships version 4.0 which builds fine with GCC 15, no patching needed.
https://github.com/sagemath/sage/pull/40153
updates it to 4.0.0.0, please review
>
> El viernes, 23 de mayo de 2025 a las 17:38:00 UTC+2, dim...@gmail.com
> escribió
Hi, can we get arch's patch into Sage?
On May 23, 2025 3:19:22 AM CDT, Antonio Rojas wrote:
>Install planarity from the Arch repos. The bundled version is not
>compatible with GCC 15
>
>El viernes, 23 de mayo de 2025 a las 9:39:36 UTC+2, benjami...@gmail.com
>escribió:
>
>> I get and error whil
Here is the update PR: https://github.com/sagemath/sage/pull/40132
On Mon, May 19, 2025 at 5:19 PM Dima Pasechnik wrote:
>
> On Mon, May 19, 2025 at 4:00 PM Antonio Rojas wrote:
> >
> > The bug is in m4ri, not in brial. It is fixed in 20250128, sage shouldn't
> >
; I've opened a Brial issue here:
>> https://github.com/BRiAl/BRiAl/issues/58
>>
>> Can we get a stand-alone Brial reproducer for this bug?
>>
>> On Mon, May 19, 2025 at 1:25 PM Grégory Vanuxem wrote:
>> >
>> > Hello here,
>> >
>> >
I've opened a Brial issue here:
https://github.com/BRiAl/BRiAl/issues/58
Can we get a stand-alone Brial reproducer for this bug?
On Mon, May 19, 2025 at 1:25 PM Grégory Vanuxem wrote:
>
> Hello here,
>
> Le lun. 19 mai 2025, 19:57, Dima Pasechnik a écrit :
>>
>&g
On Sat, May 17, 2025 at 10:43 AM chris wuthrich
wrote:
>
> Upgrading to ubuntu 25.04 also broke sage build (both 10.6 and 10.7.beta3)
> for me. Logs attached.
This is basically the error in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093321
for brial/polybori
g++: error: @SIMD_CFLAGS@:
It's broken - you need to use a recent 10.7 beta, where in particular lcalc
was updated to version 2.1.0.
On Sun, May 18, 2025, 07:11 Sette Diop wrote:
> Hi:
>
>
> I am building sage-10.6 on macOS Sequoia 15.5 and run through this error:
>
> Error building Sage.
>
>
> The following package(s) m
Well, numpy 1 isn't going to be be supported well on Python 3.13, so that's
a bit moot one way or another. I don't think Debian is working on updating
their SageMath package (and Ubuntu never had its own SageMath effort, I
think)
We have only ourselves to blame for stalling on Debian effort. Until
On Mon, May 5, 2025 at 11:56 AM Vincent Macri
wrote:
> I think just before configure, but I didn't do any testing to verify
> that's the only place you need it. I just ran it once then did all the
> steps to build from source without closing the terminal.
>
By right, once ./configure is run,
./configure without `--enable-system-site-packages` will ignore most Python
packages on its list of dependencies.
`./configure --enable-system-site-packages` wil try to use the latter, but
it might run into a version conflict.
(because most Linux distros don't have the complete range of these
avail
We still support external numpy 1.x.y, but it comes at a price.
Let's drop it?
https://github.com/sagemath/sage/issues/40050
Dima
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, se
we're getting there, see
https://github.com/sagemath/sage/pull/39977 (needs review)
https://github.com/sagemath/sage/pull/39985
https://github.com/sagemath/sage/pull/40033
On Thu, May 1, 2025 at 6:50 PM Nils Bruin wrote:
> I'm getting this error from configure for sage:
>
> real_configure: Inst
Hi David,
I already mentioned that 10.6 release is broken.
Please use the latest beta (and perhaps you will need more not yet merged
patches)
Dima
On 1 May 2025 15:06:17 GMT-05:00, David Kohel wrote:
>Hi everyone,
>
>Indeed, here is the relevant error line:
>
>../../src/sage/graphs/base/boost_i
For some reason, my proposal to release 10.6.1 to specifically fix this has
fallen on deaf ears, I don't know why.
Instead I'm sending dozens of messages related to the 10.6 problem, thank
you, the community, for the trust you place in me :-)
On Thu, May 1, 2025 at 11:18 AM Gareth Ma wrote:
> Re
It's hard to tell, but does your environment use Apple's toolchain, or Conda
toolchain.
Could it be that you forgot to activate the Conda environment?
Anyhow, I think 10.6 release is somewhat broken.
Try the latest beta instead.
Duma
On 1 May 2025 09:06:00 GMT-05:00, Gareth Ma wrote:
>Hi all,
On Wed, Apr 30, 2025 at 11:42 AM Dima Pasechnik wrote:
> Hi John,
>
> Flint is already on 3.2.2, see https://github.com/flintlib/flint
> If could be that your Flint beta is buggy, and you need 3.2.2
>
>
> We should upgrade to it, if possible.
> Singular is now 4.4.1 -
That's a different Pipfile, added in a9f8401ef643
On Wed, Apr 30, 2025 at 11:48 AM 'tobia...@gmx.de' via sage-devel <
sage-devel@googlegroups.com> wrote:
> I'd already removed this in a merged PR
> https://github.com/sagemath/sage/pull/39031. No idea why this file is now
> back. Feel free to open
Hi John,
Flint is already on 3.2.2, see https://github.com/flintlib/flint
If could be that your Flint beta is buggy, and you need 3.2.2
We should upgrade to it, if possible.
Singular is now 4.4.1 - not 100% sure whether an upgrade is feasible.
I know that flint 3.1.3 is working with Singular 4.4
There is no need to build Sage's Python, an external Python will always do.
(We have at last agreed that this mostly broken capability of Sage, to
build its own Python,
should be removed, as it mostly leads to such annoyances)
I suggest to install enough system packages, as suggested by the
./conf
d and packaged with the signed notarized pkg installers.
>
> - Marc
>
>
> On Mon, Apr 28, 2025 at 2:30 PM Isuru Fernando wrote:
>
>> Marc, do you mind trying out
>> https://github.com/3-manifolds/Sage_macOS/pull/82 ?
>>
>> Isuru
>>
>> On Sat, Apr 26
On Mon, Apr 28, 2025 at 1:20 PM Nils Bruin wrote:
> I ran into the following worrisome example. In
> sage.rings.finite_rings.element_base we have that is_FiniteFieldElement(x)
> has a deprecation on it:
>
>deprecation(32664, "the function is_FiniteFieldElement is deprecated;
> use isinstance(
On Tuesday, April 22, 2025 at 11:42:21 AM UTC-5 Michael Orlitzky wrote:
On 2025-04-22 10:19:54, Dima Pasechnik wrote:
>
> That's the first time I see a complaint that the Apple's libraries used
for
> Python or its modules are not accepted.
> This is something we can
On Thu, Apr 24, 2025 at 4:35 PM Nils Bruin wrote:
> I tried a conda-based install because I wanted to try some development on
> a machine with questionable rerequisites. Indeed, conda provided all
> prereqs very smoothly. On
>
> https://doc.sagemath.org/html/en/installation/conda.html
>
> the use
-64.so.2 (0x7f3336169000)
> libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
> (0x7f33351d4000)
>
> On Thu, 24 Apr 2025 at 22:48, Dima Pasechnik wrote:
>
>>
>>
>> On Thu, Apr 24, 2025 at 12:02 PM Aram Dermenjian <
>> aram.dermenjian.m.
;/sage/sd/src/sage/groups/libgap_mixin.py", line 15, in
> from sage.libs.gap.libgap import libgap
> ImportError: /sage/sd/src/sage/libs/gap/
> libgap.cpython-312-x86_64-linux-gnu.so: undefined symbol: GAP_CollectBags
>
Sage needs GAP 4.13 or newer.
Assuming you actually built G
Sage 10.6 was released with numpy 2.2.3, and matplotlib 3.8.0 from 2023,
which is incompatible with numpy 2 (the compatibility was added in 3.8.4).
While 10.6.rc0 was released, this problem was noticed (see
https://groups.google.com/g/sage-release/c/TkPM0xL2fFA/m/LB0dT9PLAwAJ)
but was not acted upo
The matplotib vs meson-python issue is pure madness, see
https://github.com/sagemath/sage/pull/39789
The problem is not that one cannot build matplotlib spkg. It does work on
systems we tested, and the release manager agreed.
That something does not match on PyPI is not an argument. We don't use
You can try to restart make after you hit ctrl-C. Sometimes it just works.
> Also, I'm thinking I should create a ticket along the lines of "if unable
to download xxx, then an error should be thrown instead of just hanging and
waiting forever",
it might help to trim the list of mirrors in upstrea
On Thu, Apr 24, 2025 at 1:26 AM Aram Dermenjian <
aram.dermenjian.m...@gmail.com> wrote:
> Yes, that's what I'm currently trying to do, but finding all the packages
> with wrong checksums is turning out to not be so fun. Have to keep
> rerunning `make` to try and see which package breaks next.
>
>
On Wed, Apr 23, 2025 at 11:07 AM Marc Culler wrote:
>
>
> On Monday, April 21, 2025 at 9:12:01 AM UTC-5 Michael Orlitzky wrote:
>
> IIRC you are building everything (except python, now) from SPKGs. If
> so and if you are sure that your newly-built python was linked against
> the sage copies of bz
;> probably outperforms the sage spkg version of numpy on macOS.
>>
>> But this is really another topic. Sorry. We should stick to discussing
>> the python3 spkg.
>>
>> - Marc
>>
>> On Tue, Apr 22, 2025 at 11:21 AM Dima Pasechnik
>> wrote:
&g
On Tue, Apr 22, 2025 at 8:53 AM Marc Culler wrote:
> Here is one thing that I find strange. The only external libraries that
> are needed to compile python on macOS are openssl and (if you want the real
> gnu thing) readline. I know, because I have compiled python on macOS. The
> dependencies
On Mon, Apr 21, 2025 at 9:41 PM Marc Culler wrote:
> Thank you Michael,
>
> My first guess is that
> SAGE_SPKG_DEPCHECK([bzip2 liblzma libffi zlib], ...
>
>
> I think that your guess is correct.
>
> IIRC you are building everything (except python, now) from SPKGs. If
> so and if you are sure that
On Sun, Apr 20, 2025 at 4:26 PM Marc Culler wrote:
> I got the impression from comments in this thread that it would be
> possible to build python with the prefix directory of my choice and use
> that python as the "system python" for a build of Sage. So I built a
> relocatable python 3.13 and i
On Fri, Apr 18, 2025 at 6:32 PM William Stein wrote:
> On Fri, Apr 18, 2025 at 4:12 PM Nils Bruin wrote:
> >
> > On Friday, 18 April 2025 at 10:07:12 UTC-7 dim...@gmail.com wrote:
> >
> > Nobody is going to "break" anything. You'll just need a proper Python to
> install Sage, like one of many pr
Nobody is going to "break" anything. You'll just need a proper Python to
install Sage, like one of many pre-reqs already needed.
It's just fear-mongering. Building Sage will be less broken this way, not
more broken.
Dima
On Fri, Apr 18, 2025 at 2:14 AM Sébastien Labbé wrote:
> I have been readi
On Mon, Apr 14, 2025 at 12:33 PM John H Palmieri
wrote:
> It seems that the most recent version of patch in homebrew no longer
> provides automatic access to a binary "patch" (which I think it used to
> do); instead it says
>
> If you need to use it as "patch", you can add a "gnubin" director
While you can download the tarfile from
https://ftp.gnu.org/gnu/patch/patch-2.7.6.tar.gz into upstream/
it's more economic to use Homebrew for patch, and many more dependencies.
PS. I gather that macOS patch is good enough nowadays, and we can use
it, as proposed on https://github.com/sagemath/sag
On Mon, Apr 14, 2025 at 10:58 AM Nils Bruin wrote:
>
> It looks like a is an element of "Qbar". Elements there are tracked by
> keeping track of a way to compute a polynomial it is a root of as well as a
> complex "ball" that allows one to distinguish it from other roots of the
> polynomial. Ce
On 12 April 2025 14:33:03 GMT-05:00, Marc Culler wrote:
>On Sat, Apr 12, 2025 at 1:01 PM Nils Bruin wrote:
>
>I get the impression that the concern is about maintenance load: when the
>> project takes on the commitment to build python then it must update the
>> python build package whenever th
On Fri, Apr 11, 2025 at 5:55 PM Marc Culler wrote:
>
> If we can get back to the original topic of this thread, I would like to
> report on the experiment I just finished. That experiment was to update the
> python3 spkg to Python-3.13.3 (the latest python release) and then build Sage
> 10.7.b
On 11 April 2025 11:28:17 GMT-05:00, Marc Culler wrote:
>
>
>On Thursday, April 10, 2025 at 9:53:04 PM UTC-5 Tobias wrote:
>
>
>With all non-python pre-reqs in place,
>just run./bootstrap and pip to build sagelib, that's all.
>No need to worry about a dodgy custom venv,
>unhappy ./configure,
On Thu, Apr 10, 2025 at 5:41 PM Michael Orlitzky wrote:
>
> On 2025-04-10 12:10:07, Nathan Dunfield wrote:
> >
> > Interesting, where can I find a list of the non-python pre-reqs?
>
> "meson setup" should tell you. Some of the dependency checks it does
> are not as precise as the corresponding che
On Thursday, April 10, 2025 at 2:10:07 PM UTC-5 Nathan Dunfield wrote:
On Thursday, April 10, 2025 at 9:37:09 AM UTC-5 Dima wrote:
On 10 April 2025 07:45:09 GMT-05:00, I wrote:
>To me, a "proper Python package" is something I can install with
>"random-python -m pip install blah" that pulls a
On Tue, Apr 8, 2025 at 9:55 AM Léon Vaia wrote:
>
> Thank you very much Dima.
>
> Trying to run
> sudo apt-get libffi-dev xz-utils liblzma-dev
> I get
> E: Invalid operation libffi-dev
oops, sorry, it should have been
sudo apt-get install libffi-dev xz-utils liblzma-dev
>
> Installing the d
On Monday, April 7, 2025 at 10:59:40 AM UTC-5 marc@gmail.com wrote:
As this discussion tries to wander off into a new discussion about the uv
project, I will attempt to bring it back on topic.
The point is this: Currently, to build the macOS binary, we first build
sage in a completely st
On 10 April 2025 07:45:09 GMT-05:00, Nathan Dunfield
wrote:
>On Thursday, April 10, 2025 at 12:07:03 AM UTC-5 Dima wrote:
>
>> Probably not on the build system. But the app needs to work on *any*
>system.
>>
>>> Are you worried that sage would have trouble recognizing the python
>build as
On Wed, Apr 9, 2025 at 10:21 PM Marc Culler wrote:
>
> On Wed, Apr 9, 2025 at 8:07 PM Nils Bruin wrote:
>>
>> On Monday, 7 April 2025 at 08:59:40 UTC-7 marc@gmail.com wrote:
>>
>> If the Python spkg were removed we would no longer be able to start from a
>> standard build of Sage.
>>
>> Can
On 9 April 2025 18:54:13 GMT-05:00, Nils Bruin wrote:
>On Wednesday, 9 April 2025 at 16:44:31 UTC-7 dim...@gmail.com wrote:
>
>As I already explained, it's quite a stretch by Sage's standards to call
>python3 package standard. Because it is not tested enough;
>because few months into release,
On Wed, Apr 9, 2025 at 9:05 AM Marc Culler wrote:
>
>
>
> On Monday, April 7, 2025 at 11:48:15 PM UTC-5 Dima wrote:
>
> Besides, Nils' proposal would mean to introduce an entirely new kind of Sage
> package,
>
>
> No, it wouldn't. It would make a small change to how one existing configure
> op
This looks like the report from
https://groups.google.com/g/sage-release/c/fbtK6VeIikE/m/zhJp0MtgCQAJ
(which also suggests fixes etc)
On Tue, Apr 8, 2025 at 9:55 AM Zeke wrote:
>
> I'm having trouble building sage, encountering errors for the below packages.
>
> 1. for both singular and gfan
>
>
On Mon, Apr 7, 2025 at 5:12 PM Marc Culler wrote:
>
>
>
> On Mon, Apr 7, 2025 at 3:25 PM Dima Pasechnik wrote:
>>
>>
>> It's not standard - no-one nowadays builds Sage's Python, not even CI is
>> doing this.
>>
>> This is the point I a
It is likely the case, but this is exactly my point - we don't want to spend
our and other people time on solving a problem no other python package out
there is doing - building Python from source.
I am all ears as far as needs of building macOS app is concerned, I am willing
to spend my time o
Could you please post the top-level config.log
On 7 April 2025 01:19:21 GMT-05:00, "Léon Vaia"
wrote:
>
>Output of python3 on wsl terminal:
>Python 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] on linux
>Type "help", "copyright", "credits" or "license" for more information.
>
>Output
On 7 April 2025 07:48:37 GMT-05:00, Nathan Dunfield
wrote:
>
>
>1) Having sagemath detect python version requirements and build its own if
>not acceptable version is found leads to increased support requests.
>
>[...]
>
>It seems to me that for 1) it isn't so important if python occurs as an
On Sun, Apr 6, 2025 at 6:07 PM Marc Culler wrote:
>
> This is surely not the place for a long technical discussion of the problems
> that have to be solved to produce the macOS app. Let me just mention one
> item at the tip of the iceberg, ignoring, for example, how we go about
> making sage
Are you not mixing up Python installed in Windows with Python installed in WSL?
In WSL terminal, what is the output of
python3
command?
What is the output of
echo $PATH
command?
On 6 April 2025 04:52:03 GMT-05:00, "Léon Vaia"
wrote:
>I already installed it, as python3, and it is
On 6 April 2025 11:41:21 GMT-05:00, Nils Bruin wrote:
>It looks to me that there are two points of view here.
>
>1) Having sagemath detect python version requirements and build its own if
>not acceptable version is found leads to increased support requests.
I repeat - it is not only increased
export PATH=/opt/homebrew/bin:$PATH # on arm64
(on Intel, do
export PATH=/usr/local/bin:$PATH
instead)
source .homebrew-build-env
./configure
should work
On 5 April 2025 12:42:09 GMT-05:00, Tagir Eminov
wrote:
>i did:
>source .homebrew-build-env
>./config (tried with python modules flag)
Oh, this is yet another example of the harm caused by the presence of Python
spkg, this time on Ubuntu in WSL.
Can you install Python from the system (it has to be Python 3.11 or newer,
possibly you need to use a ppa, if there is no official Python 3.11 package
available),
and use it, instead o
Do you use Homebrew?
Please post top-level config.log
On 29 March 2025 01:29:35 GMT-05:00, 'Vishal Shahi' via sage-devel
wrote:
>
>
>Dear Sage Development Team,
>
>I am experiencing an issue while building Sage on my MacBook Air M1 running
>macOS Sequoia. I followed all instructions outlined in
Please send the top level config.log too, as asked at the end of the log file
you attached
On 4 April 2025 19:02:18 GMT-05:00, "Léon Vaia"
wrote:
> Dear Sage Development Team,
>
>I have an issue while building Sage from source.
>I'm doing it on a Dell XPS 13 on WSL with Ubuntu.
>
>I attach the
On Tue, Apr 1, 2025 at 10:26 AM chris wuthrich
wrote:
>
>
> Would that mean that users (like me) will have to downgrade python provided
> by their distribution at times - or to learn how to use multiple version of
> python?
Using multiple versions of python is not a dark art. You install it
wit
Please install gcc, g++, and gfortran as your OS packages.
Don't try to build Sage's gcc/gfortan, it's broken and, frankly,
overdue to be removed. What's available from OS should suffice in all
cases.
HTH
Dima
On Fri, Apr 4, 2025 at 12:07 PM Raúl Penaguião wrote:
>
> Dear Sage Development Team,
We're discussing this issue here:
https://github.com/sagemath/sage/issues/39740
which seems to progress forward
On Friday, March 21, 2025 at 12:00:39 AM UTC-5 verner.a...@gmail.com wrote:
>
> Hello,
>
> I'm experiencing difficulties with using SageMath as a Python package. In
> particular, to
ource(*ei, graph)],
+to_return.push_back({static_cast(index[boost::source(*ei,
graph)]),
{index[boost::target(*ei, graph)],
get(boost::edge_weight, graph, *ei)}});
}
l
On Tue, Apr 1, 2025 at 2:32 PM Dima
On Thu, Apr 3, 2025 at 5:48 PM Marc Culler wrote:
>
> This will unnecessarily make it more difficult to build the Sage_mac OS
> binary package. In order to make that package easy to install in the way
> that normal macOS users expect, it must be signed and notarized. In order to
> notarize t
On Fri, Apr 4, 2025 at 6:54 AM 'tobia...@gmx.de' via sage-devel
wrote:
>
> Thanks for your interest, William!
>
> The Meson project for Sage began in October 2023 (PR #36524), and most of the
> work was wrapped up a couple of months ago. I just wanted to iron out a few
> remaining annoyances bef
On 3 April 2025 17:48:00 GMT-05:00, Marc Culler wrote:
>This will unnecessarily make it more difficult to build the Sage_mac OS
>binary package. In order to make that package easy to install in the way
>that normal macOS users expect, it must be signed and notarized. In order
>to notarize the p
On Thu, Apr 3, 2025 at 7:51 AM William Stein wrote:
> Congrats and fantastic! Is it possible that you could add some
> additional "human context" for those of us on the sidelines, e.g., who
> added Meson support to Sage (you?), why?, how hard what is and how
> long did it take?, what was involv
ssue!
>
> On Fri, 7 Mar 2025 at 09:31, Vincent Delecroix
> <20100.d...@gmail.com> wrote:
> >
> > Thanks Dima for the pointers.
> >
> > Note that it does not exactly solve the issue in the "dirty short term
> > way" since images depends on ferret
I think this is fixed by https://github.com/sagemath/sage/pull/39850 (where
I correctly identify the cause)
On Tuesday, April 1, 2025 at 2:43:17 PM UTC-5 Dima Pasechnik wrote:
> Hi,
> yes, I can reproduce this problem with a fresh Conda. That is, our
> instructions
>
> https://d
ly
> > caused by different translation units being compiled with different
> > visibility settings.
Dima
On Tue, Apr 1, 2025 at 1:50 PM Dima Pasechnik wrote:
>
> Once again, what Sage version are you using? 10.6 was just released
> (it's basically the same as 10.6.rc1)
>
On Tue, Apr 1, 2025 at 10:57 AM David Lowry-Duda wrote:
>
> On 10:50 Tue 01 Apr 2025, Trevor Karn wrote:
> >This is my concern. But if there is a way to use only system python
> >installed following https://www.python.org/about/gettingstarted/ without
> >regard to version issues, and get rid of SP
On Mon, Mar 31, 2025 at 11:45 PM Travis Scrimshaw wrote:
>
> > 1. Are we allowed to have the latex engine set for xelatex and assume the
> > user has this feature (if they care about compiling the pdf doc)? (The only
> > other exception is uplatex for the Japanese docs.) If not, do we want to
>
1 - 100 of 4228 matches
Mail list logo
