On Mac OS 13.4 with Intel Core i5 and upgraded homebrew, it compile from
the first built.
For make ptestlong, I had
--
sage -t --long --warn-long 223.1
--random-seed=206611625835564763015916265621072613635
Probably introduced in #35619
On Sunday, May 28, 2023 at 5:06:10 PM UTC-7 John H Palmieri wrote:
> stdin.info is not in the tarball, but rather produced by `./configure`.
> My best guess it that it's created somewhere in the check for the SPKG
> "info".
>
> On Sunday, May 28, 2023 at 3:16:49
stdin.info is not in the tarball, but rather produced by `./configure`. My
best guess it that it's created somewhere in the check for the SPKG "info".
On Sunday, May 28, 2023 at 3:16:49 PM UTC-7 Volker Braun wrote:
> The spurious stdin.info in the tarball can be deleted, obviously
> shouldn't
The spurious stdin.info in the tarball can be deleted, obviously shouldn't
be there
On Sunday, May 28, 2023 at 10:10:23 PM UTC+2 John H Palmieri wrote:
> On OS X: after running `./configure`, I see
>
> % git status
> On branch develop
> Your branch is up to date with 'upstream/develop'.
>
>
On OS X: after running `./configure`, I see
% git status
On branch develop
Your branch is up to date with 'upstream/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
stdin.info
nothing added to commit but untracked files present (use "git add" to track)
On
