[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikBDVR=S5J-=Kjq1QW3OU64WzHYRg@mail.gmail.com>
Date: Wed, 15 Jun 2011 11:19:48 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Michael Ellerman <michael@...erman.id.au>
Cc: Linux Kernel Development <linux-kernel@...r.kernel.org>,
Linux-Next <linux-next@...r.kernel.org>
Subject: Re: Build regressions/improvements in v3.0-rc3
On Wed, Jun 15, 2011 at 11:11, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.0-rc3[1] compared to v2.6.39[2].
>
> Summarized:
> - build errors: +21/-66
> - build warnings: +202/-421
>
> JFYI, when comparing v3.0-rc3 to v3.0-rc2[3], the summaries are:
> - build errors: +20/-45
> - build warnings: +92/-101
While looking what kind of fix got applied for one of the
improvements, I noticed it
didn't get fixed at all. But m68k/allmodconfig is broken due to an
unrelated change, after
which the build stops, so it never got to compile the file I was looking into.
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 ;-)
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists