Sage 9.3 has been released.
Try it and not 9.2 please.
On Tue, 18 May 2021, 06:27 Mike Lensi, wrote:
> I seem to be having a similar issue. Are there any new recommendations?
>
> On Wednesday, October 7, 2020 at 8:39:59 AM UTC-6 wdjo...@gmail.com wrote:
>
>> Hi:
>>
>> The compiler still can't
I seem to be having a similar issue. Are there any new recommendations?
On Wednesday, October 7, 2020 at 8:39:59 AM UTC-6 wdjo...@gmail.com wrote:
> Hi:
>
> The compiler still can't find installed python3:
>
> wdj@jeeves sage-9.2.rc0 % which python3
>
>
On Thu, Oct 8, 2020 at 2:47 PM slelievre wrote:
> 2020-10-08 17:38:08 UTC, David Joyner:
> >
> > I can log in but don't seem to have permission to add a comment to trac.
>
> Your trac account was missing a name and an email.
> I filled those in, can you try again?
>
That must have worked, thank
2020-10-08 17:38:08 UTC, David Joyner:
>
> I can log in but don't seem to have permission to add a comment to trac.
Your trac account was missing a name and an email.
I filled those in, can you try again?
--
You received this message because you are subscribed to the Google Groups
On Thu, Oct 8, 2020 at 9:48 AM slelievre wrote:
> 2020-10-07 21:09:18 UTC, John H Palmieri:
> >
> > including details of which homebrew packages you've installed.
>
> To get your installed homebrew packages listed in a file:
> ```
> $ brew list --versions > brew-list-versions.txt
> ```
>
Thank
2020-10-07 21:09:18 UTC, John H Palmieri:
>
> including details of which homebrew packages you've installed.
To get your installed homebrew packages listed in a file:
```
$ brew list --versions > brew-list-versions.txt
```
Or to add the date to the filename:
```
$ brew list --versions >
I would suggest not to touch macOS 11 until it is running Homebrew (or help
them), because they basically have the same issues to solve.
On Wed, 7 Oct 2020, 22:09 John H Palmieri, wrote:
> I think you should report this at #30651, including details of which
> homebrew packages you've
I think you should report this at #30651, including details of which
homebrew packages you've installed. It was suggested at
https://trac.sagemath.org/ticket/30494#comment:92 that homebrew's gfortran
may not work with Big Sur, so you might want to install Sage's version of
that, too.
On
On Wed, Oct 7, 2020 at 12:37 PM David Lowry-Duda
wrote:
> sage -f [opts] [packages] is a shortcut for force-building specified
> packages. If you examine the output of `sage -advanced` on a commandline,
> this is noted there. The command `sage -advanced` is a more complete
> version of the
On Wed, Oct 7, 2020 at 1:06 PM John H Palmieri
wrote:
> Building Sage on Big Sur is being tracked at
> https://trac.sagemath.org/ticket/30651; see also
> https://trac.sagemath.org/ticket/30494. Do you have homebrew installed,
> and if so, which packages? You could try forcing Sage to build its
Building Sage on Big Sur is being tracked at
https://trac.sagemath.org/ticket/30651; see also
https://trac.sagemath.org/ticket/30494. Do you have homebrew installed, and
if so, which packages? You could try forcing Sage to build its own zlib,
for example, to try to get Sage's Python to find
sage -f [opts] [packages] is a shortcut for force-building specified
packages. If you examine the output of `sage -advanced` on a commandline,
this is noted there. The command `sage -advanced` is a more complete
version of the typical help command `sage -h`.
(I don't know how to solve your
On a lark, I ran ./sage -f
This is undocumented as far as I can tell
and I've no idea what it does (of course ./sage doesn't
work since it didn't compile - see my previous email
in this thread). It seemed to try to compile
python 3.8.5. I pasted the tail end below, in case this
is useful. BTW,
13 matches
Mail list logo
