Thanks Matthias.

This is on the latest develop branch.

I have added a comment to the ticket you mention.

Guillermo

On Mon, 25 Apr 2022 at 04:32, Matthias Koeppe <matthiaskoe...@gmail.com>
wrote:

> Which version of Sage is this?
> We fixed a bug like this recently that showed up when the environment
> variable MAKE was set in a particular way.
> See also https://trac.sagemath.org/ticket/33587
>
> On Sunday, April 24, 2022 at 3:17:08 AM UTC-7 list...@gmail.com wrote:
>
>>
>> Thanks, Maxime.
>>
>> Here is what I did.
>> Starting from scratch, cloned develop branch, make, make pytest, make
>> ptestlong with no problems.
>> New branch with a very minor modification in one file (typo in a doc
>> string).
>> So I think this applies:
>>
>> *Rebuilding Sage*
>> Once you have made any changes you of course want to build Sage and try
>> out your edits. As long as you only modified the Sage library (that is,
>> Python and Cython files under src/sage/...) you just have to run:
>> ./sage -br
>> to rebuild the Sage library and then start Sage. This should be quite
>> fast. If you made changes to third-party packages, then you have to run
>> make build
>> as if you were installing Sage from scratch.
>>
>>  Of course make build works, but my question is why ./sage -br fails with
>> /bin/sh: @cd: command not found
>>
>> Guillermo
>>
>> On Sun, 24 Apr 2022 at 11:30, Maxime Bombar <maxime...@inria.fr> wrote:
>>
>>> On 4/24/22 00:37, G. M.-S. wrote:
>>> >
>>> > Following the advice in
>>> >
>>> >
>>> https://doc.sagemath.org/html/en/developer/walk_through.html#rebuilding-sage
>>> >
>>> > when trying
>>> >
>>> > ./sage -br
>>> >
>>> > I get
>>> >
>>> > [...]
>>> > ***********************************************
>>> > /bin/sh: @cd: command not found
>>> > make: *** [sagelib-SAGE_VENV-no-deps] Error 127
>>> >
>>> > real 0m0.029s
>>> > user 0m0.024s
>>> > sys 0m0.003s
>>> > ***************************************************************
>>> > Error building Sage.
>>> >
>>> > The following package(s) may have failed to build (not necessarily
>>> > during this run of 'make sagelib-no-deps'):
>>> >
>>> > It is safe to delete any log files [...]
>>> >
>>> > What can I do?
>>> >
>>> > Guillermo
>>> >
>>> Hi Guillermo,
>>>
>>> if you have upgraded your system, especially python version, and/or
>>> other Sage dependencies, it might be necessary to rebuild sage from
>>> scratch, with a `make build`.
>>>
>>> --
>>> Maxime
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-support/275b0149-3c16-4b83-a196-a8d0f1170ecen%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-support/275b0149-3c16-4b83-a196-a8d0f1170ecen%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CANnG18-a7iRoxwMWz3XE3_V22UBN68JzHVC1PQjE_R58frV4Qw%40mail.gmail.com.

Reply via email to