From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc3
Date: Mon, 28 Sep 2015 10:30:06 +0100 [thread overview]
Message-ID: <20150928093006.GT21513@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdWrBYnQ0CRYmBgO3xNZMqCY42OtNwhryqzi+Tv+KGj6Lg@mail.gmail.com>
On Mon, Sep 28, 2015 at 08:57:44AM +0200, Geert Uytterhoeven wrote:
> On Sun, Sep 27, 2015 at 9:34 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v4.3-rc3[1] to v4.3-rc2[3], the summaries are:
> > - build errors: +8/-12
>
> + error: No rule to make target include/config/auto.conf: => N/A
>
> arm-randconfig
Not every randconfig failure is a kernel problem. Here's an example:
Physical address of main memory (PHYS_OFFSET) [] (NEW) aborted!
Console input/output is redirected. Run 'make oldconfig' to update configuration.
This needs someone to provide a value, which means these failures are
not in fact failures of the kernel, but a failure of the build system
to anticipate that there may be Kconfig questions that need input.
So, these ones should be ignored.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-09-28 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 19:34 Geert Uytterhoeven
2015-09-28 6:57 ` Geert Uytterhoeven
2015-09-28 9:30 ` Russell King - ARM Linux [this message]
2015-09-28 9:48 ` Russell King - ARM Linux
2015-09-28 13:50 ` Geert Uytterhoeven
2015-09-28 13:58 ` Russell King - ARM Linux
2015-09-28 14:08 ` Geert Uytterhoeven
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=20150928093006.GT21513@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®