New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always use V=1 for logfiles #22418
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Commit: |
New commits:
|
comment:7
This looks fine; but I just noticed that (with or without this ticket) this works for |
comment:8
Replying to @mkoeppe:
That is a different issue which is unrelated to this ticket. |
Reviewer: Matthias Koeppe |
Changed branch from u/jdemeyer/always_use_v_1_for_logfiles to |
comment:11
Follow-up: #22492 |
Changed commit from |
With #21539, Sage globally supports a
V=0
mode. In this mode, the individual logfiles are created withV=1
. But this leads to surprising behaviour because some packages haveV=0
by default. So a build withV=0
can actually be more verbose than a build withV
unset.Instead, always unconditionally use
V=1
for individual packages.CC: @mkoeppe
Component: build
Author: Jeroen Demeyer
Branch:
dcc3ba5
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/22418
The text was updated successfully, but these errors were encountered: