On Friday, July 31, 2020 at 5:12:23 PM UTC-7, Samuel Lelievre wrote:
>
>
> Is the following another instance of the same broken logic?
>
> Configuring with
> ```
> $ ./configure
> --with-system-gmp=no \
> --with-system-mpir=no \
> --with-mp=mpir \
> ```
> leads to both gmp and mpir be
2020-07-31 23:03 UTC, Matthias Koeppe:
>
> On Friday, July 31, 2020 at 3:51:45 PM UTC-7, Dima Pasechnik wrote:
>>
>> On Fri, Jul 31, 2020 at 11:41 PM Samuel Lelièvre:
>> >
>> > 2020-07-31 22:26 UTC, Dima Pasechnik:
>> > > >> I decided to configure with
>> > > >>
>> > > >> --with-system-gcc=no -
Quotes are your friend. Try
sage: cd "test-123"
It would be virtually impossible to adapt the preparser in a reasonable way
to recognize this exceptional pattern. We'd basically have to teach it
these specific prefixes. If we ever look at hooking preparsing somewhere
else, then this might be
On Friday, July 31, 2020 at 3:51:45 PM UTC-7, Dima Pasechnik wrote:
>
> On Fri, Jul 31, 2020 at 11:41 PM Samuel Lelièvre
> > wrote:
> >
> > 2020-07-31 22:26 UTC, Dima Pasechnik:
> > > >> I decided to configure with
> > > >>
> > > >> --with-system-gcc=no --with-system-gfortran=no
> > >
>
On Fri, Jul 31, 2020 at 11:41 PM Samuel Lelièvre
wrote:
>
> 2020-07-31 22:26 UTC, Dima Pasechnik:
> >
> > On Fri, Jul 31, 2020 at 10:55 PM Matthias Koeppe:
> > >
> > > That's a bug. Please open a ticket
> > >
> > > On Friday, July 31, 2020 at 2:44:08 PM UTC-7, Samuel Lelievre wrote:
> > >>
> > >>
2020-07-31 22:26 UTC, Dima Pasechnik:
>
> On Fri, Jul 31, 2020 at 10:55 PM Matthias Koeppe:
> >
> > That's a bug. Please open a ticket
> >
> > On Friday, July 31, 2020 at 2:44:08 PM UTC-7, Samuel Lelievre wrote:
> >>
> >> Dear sage-devel,
> >>
> >> On macOS, alongside my attempts to build Sage
> >>
On Fri, Jul 31, 2020 at 10:55 PM Matthias Koeppe
wrote:
>
> That's a bug. Please open a ticket
>
> On Friday, July 31, 2020 at 2:44:08 PM UTC-7, Samuel Lelievre wrote:
>>
>> Dear sage-devel,
>>
>> On macOS, alongside my attempts to build Sage
>> using as many Homebrew packages as possible,
>> I am
2020-07-31 22:00 UTC, Matthias Koeppe:
>
> "maximal" is already defined and does what you want.
> (We use it in the tests for builds of optional/experimental
> packages -- see for example
> https://github.com/sagemath/sage/actions/runs/182648184)
>
> What is missing is the package lists in
> build/
On Friday, July 31, 2020 at 7:58:27 AM UTC-7, Samuel Lelievre wrote:
>
> Currently for each distro we have two tox environments:
>
> - minimal: has the minimal amount of packages for Sage to build
> - standard: has all the packages Sage knows how to use
>
> but we might be missing:
>
> - maximal: h
That's a bug. Please open a ticket
On Friday, July 31, 2020 at 2:44:08 PM UTC-7, Samuel Lelievre wrote:
>
> Dear sage-devel,
>
> On macOS, alongside my attempts to build Sage
> using as many Homebrew packages as possible,
> I am trying to build a "batteries-included" Sage
> completely independent
Dear sage-devel,
On macOS, alongside my attempts to build Sage
using as many Homebrew packages as possible,
I am trying to build a "batteries-included" Sage
completely independent of Homebrew.
I decided to configure with
--with-system-gcc=no --with-system-gfortran=no
and was expecting the f
> On Jul 31, 2020, at 11:13, Sébastien Labbé wrote:
>
> This might be a workaround too:
>
> sage: !cd test-123
I don’t think this will work. The “!” forks a subshell where the given command
is executed, and once the command executes (so the CWD is “test-123”), the
shell exits, leaving the
Hello all,
We have just released Flint-2.6.2. This combines numerous fixes for
various platforms (included in version 2.6.1, which we didn't announce
due to more bugs surfacing) along with all remaining critical issues
that we are aware of.
The release can be downloaded from our website [1] or is
> On Jul 31, 2020, at 10:27, Neil Penning wrote:
>
> Hello, I'm new to sagemath, and I stumbled upon a bug and I don't know where
> else to report it.
>
> The preparser seems to have no problem with "cd test123" but has a problem
> with "cd test-123" (see screenshot)
Ha! I don’t know if t
Thank you both.
I'll take a stab at improving the preparse code, but these solutions sort
of make the issue moot.
On Fri, Jul 31, 2020 at 2:13 PM Sébastien Labbé wrote:
> This might be a workaround too:
>
> sage: !cd test-123
>
> --
> You received this message because you are subscribed to a t
This might be a workaround too:
sage: !cd test-123
--
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, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussio
On Fri, Jul 31, 2020 at 6:37 PM Neil Penning wrote:
>
> Hello, I'm new to sagemath, and I stumbled upon a bug and I don't know where
> else to report it.
>
> The preparser seems to have no problem with "cd test123" but has a problem
> with "cd test-123" (see screenshot)
Thanks. As a workaround,
Hello, I'm new to sagemath, and I stumbled upon a bug and I don't know
where else to report it.
The preparser seems to have no problem with "cd test123" but has a problem
with "cd test-123" (see screenshot)
--
You received this message because you are subscribed to the Google Groups
"sage-dev
Currently for each distro we have two tox environments:
- minimal: has the minimal amount of packages for Sage to build
- standard: has all the packages Sage knows how to use
but we might be missing:
- maximal: has all the packages we wish Sage knew how to use
to check Sage can at least build i
19 matches
Mail list logo
