public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] build-many-glibcs.py: Use make -O for more consistent log output
Date: Fri, 19 Feb 2021 16:14:05 -0500	[thread overview]
Message-ID: <9323419b-f0e4-e64d-d41e-b30dd0172796@redhat.com> (raw)
In-Reply-To: <87eehc9f4n.fsf@oldenburg.str.redhat.com>

On 2/19/21 11:49 AM, Florian Weimer via Libc-alpha wrote:
> 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):
> 

LGTM. Defaults to deinterlacing the output from the entire recipe (target).

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-- 
Cheers,
Carlos.


      reply	other threads:[~2021-02-19 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 16:49 Florian Weimer
2021-02-19 21:14 ` Carlos O'Donell [this message]

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=9323419b-f0e4-e64d-d41e-b30dd0172796@redhat.com \
    --to=carlos@redhat.com \
    --cc=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).