mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "'psmith@gnu.org'" <psmith@gnu.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: I disabled more compiler warnings..
Date: Mon, 11 May 2020 21:09:03 +0000	[thread overview]
Message-ID: <90909f30775744b89d1a0c40265779d9@AcuMS.aculab.com> (raw)
In-Reply-To: <0ff4860b4202a6ef3bb3b29912d083d471e1cc1d.camel@gnu.org>

From: Paul Smith
> Sent: 11 May 2020 18:59
> On Mon, 2020-05-11 at 10:41 -0700, Linus Torvalds wrote:
> > On Mon, May 11, 2020 at 12:43 AM David Laight <
> > David.Laight@aculab.com> wrote:
> > >
> > > I've not looked inside gmake, but I fixed nmake so that it
> > > properly used a single job token pipe for the entire (NetBSD)
> > > build and then flushed and refilled it with 'abort' tokens
> > > when any command failed.
> > > That made the build stop almost immediately.
> >
> > The GNU jobserver doesn't have anything like that, afaik.
> >
> > I think it always writes a '+' character as a token, so I guess it
> > could be extended to write something else for the "abort now"
> > situation (presumably a '-' character).
> 
> That was exactly my plan.

ISTR using '*' :-) Was a long time ago.

One problem is ensuring that all the recursive makes actually
use the same token queue.
The Linux kernel build acts as though the sub-makes have their
own queue - I certainly had to fix that as well.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  parent reply	other threads:[~2020-05-11 21:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 19:33 Linus Torvalds
2020-05-11  7:43 ` David Laight
2020-05-11 17:41   ` Linus Torvalds
2020-05-11 17:58     ` Paul Smith
2020-05-11 19:33       ` Linus Torvalds
2020-05-11 20:25         ` Paul Smith
2020-05-11 21:09       ` David Laight [this message]
2020-05-12  7:55         ` David Laight
2020-05-12 14:35           ` Paul Smith
2020-05-12 15:04             ` David Laight
2020-05-12 16:55               ` Paul Smith
2020-05-13  8:21                 ` David Laight
2020-05-13 15:32                   ` Paul Smith
2020-05-13 15:53                     ` David Laight
2020-05-13 16:06                       ` Paul Smith
2020-05-11  9:03 ` Arnd Bergmann
2020-05-11 11:11   ` Arnd Bergmann

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=90909f30775744b89d1a0c40265779d9@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psmith@gnu.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yamada.masahiro@socionext.com \
    /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

all inboxes | Powered by JetHome®