From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Michael Ellerman <michael@ellerman•id.au>,
Linux Kernel Development <linux-kernel@vger•kernel.org>,
Linux-Next <linux-next@vger•kernel.org>
Subject: Re: Build regressions/improvements in v3.0-rc3
Date: Sat, 18 Jun 2011 18:30:29 +1000 [thread overview]
Message-ID: <20110618183029.822f4d82.sfr@canb.auug.org.au> (raw)
In-Reply-To: <BANLkTikBDVR=S5J-=Kjq1QW3OU64WzHYRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Hi Geert,
On Wed, 15 Jun 2011 11:19:48 +0200 Geert Uytterhoeven <geert@linux-m68k•org> wrote:
>
> Would it be possible to build with `make -k', so it continues in case
> of an error, and
> tries to build as much as possible?
> Yes, I know this may increase build time considerably, but in an ideal
> world, there
> are no compile errors and everything is built anyway ;-)
Done (I think - it required very simple changes to a Python script and I
only do "monkey see, monkey do" Python programming :-))
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-18 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1106151111200.18110@ayla.of.borg>
2011-06-15 9:19 ` Build regressions/improvements in v3.0-rc3 Geert Uytterhoeven
2011-06-18 8:30 ` Stephen Rothwell [this message]
2011-06-18 12:19 ` Geert Uytterhoeven
2011-06-23 11:27 ` Stephen Rothwell
2011-06-24 6:08 ` Geert Uytterhoeven
2011-06-24 6:10 ` Stephen Rothwell
2011-06-24 14:50 ` Geert Uytterhoeven
2011-06-15 11:44 Wanlong Gao
2011-06-15 12:29 ` Build " Stephen Rothwell
2011-06-15 16:37 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2011-06-15 16:59 Wanlong Gao
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=20110618183029.822f4d82.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michael@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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