linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kbuild: Ctrl-C of parallel kernel build sometimes corrupts .o.cmd files permanently
Date: Sat, 12 Jun 2021 15:25:16 +0200	[thread overview]
Message-ID: <YMS1vNnnbPNUbsVN@gmail.com> (raw)
In-Reply-To: <CAK7LNARYuP70tz-dV+MfrpRke_3UvZ9wqqS2X8-FR9eXjcBmWQ@mail.gmail.com>


* Masahiro Yamada <masahiroy@kernel.org> wrote:

> > Hmm, I do not know why GNU Make behaves like this...
> >
> > I will ask about this in GNU Make ML.
> 
> 
> https://lists.gnu.org/archive/html/help-make/2021-06/msg00001.html
> 
> 
> In short, 'tee' was also interrupted,
> then 'make' got SIGPIPE, which terminated the app
> due to the default behavior.

So, what's the solution? It's rather common to 
run a build job while capturing a log via 'tee'. 

Ctrl-C only recently started corrupting the 
kernel build. (As in the past ~2 years ;-)


Thanks,

	Ingo

      reply	other threads:[~2021-06-12 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 15:50 kbuild: Ctrl-C of parallel kernel build sometimes corrupts .o.cmd files permanently Ingo Molnar
2021-06-02 18:20 ` Masahiro Yamada
2021-06-03 12:39   ` Ingo Molnar
2021-06-03 12:43     ` Ingo Molnar
2021-06-04  3:22       ` Masahiro Yamada
2021-06-09 13:59         ` Masahiro Yamada
2021-06-12 13:25           ` Ingo Molnar [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=YMS1vNnnbPNUbsVN@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    /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 NNTP newsgroup(s).