conda activate sage-build works nicely. Thanks!
Le lundi 9 mai 2022 à 13:20:36 UTC+2, isu...@gmail.com a écrit :
> conda activate sage-build should do the trick.
>
> Isuru
>
> On Mon, May 9, 2022 at 6:03 AM Dima Pasechnik wrote:
>
>>
>>
>> On Mon, 9 May 2022, 11:49 harald@gmail.com,
>> w
conda activate sage-build should do the trick.
Isuru
On Mon, May 9, 2022 at 6:03 AM Dima Pasechnik wrote:
>
>
> On Mon, 9 May 2022, 11:49 harald@gmail.com,
> wrote:
>
>> ... or add it to the PATH, I suppose. But how do I find it now?
>
>
> searching config.log for tachyon gives
>
> /Users
On Mon, 9 May 2022, 11:49 harald@gmail.com,
wrote:
> ... or add it to the PATH, I suppose. But how do I find it now?
searching config.log for tachyon gives
/Users/harald/miniconda3/envs/sage-build/bin/tachyon
Indeed, searching for PATH there will tell you that
Users/harald/miniconda3/env
You have built Sage with a lot of Conda packages, as can be seen from your
config.log.
Not sure you had Conda activated, but you had its binary directories in
PATH,
in particular tachyon was found there.
Now tachyon is no longer in PATH. One way to remedy this would be to
activate Conda and then s
and if you run
which tachyon
outside of "sage -sh" subshell, is it seen?
If not, it might be about activated vs non-activated Conda.
If you built Sage under Conda, you'd need to run it under Conda, too.
On Mon, 9 May 2022, 10:02 harald@gmail.com,
wrote:
> Right, "which tachyon" gives a
Right, "which tachyon" gives an empty output. What to do?
Le lundi 9 mai 2022 à 09:11:41 UTC+2, dim...@gmail.com a écrit :
> OK, so tachyon comes from Conda... Can you check that tachyon is in
> Sage's PATH, i.e.
> run the following two commands:
>
> ./sage -sh
> which tachyon
>
>
> On Sun, May 8,
OK, so tachyon comes from Conda... Can you check that tachyon is in
Sage's PATH, i.e.
run the following two commands:
./sage -sh
which tachyon
On Sun, May 8, 2022 at 11:56 PM harald@gmail.com
wrote:
>
> Here it is.
>
> Le samedi 7 mai 2022 à 19:21:24 UTC+2, dim...@gmail.com a écrit :
>>
>>
