From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] build-many-glibcs.py: Use make -O for more consistent log output
Date: Fri, 19 Feb 2021 17:49:44 +0100 [thread overview]
Message-ID: <87eehc9f4n.fsf@oldenburg.str.redhat.com> (raw)
The -O option avoids interleaving (e.g.) compiler error messages
with other build messages, and makes attribute of messages to
commands easier.
According to my tests, the impact on build time is within the noise.
---
scripts/build-many-glibcs.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 071f338cbb..8d97320f6d 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -670,7 +670,7 @@ class Context(object):
def do_build(self):
"""Do the actual build."""
- cmd = ['make', '-j%d' % self.parallelism]
+ cmd = ['make', '-O', '-j%d' % self.parallelism]
subprocess.run(cmd, cwd=self.builddir, check=True)
def build_host_libraries(self):
next reply other threads:[~2021-02-19 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:49 Florian Weimer [this message]
2021-02-19 21:14 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eehc9f4n.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).