From: Adrian Bunk <bunk@stusta.de>
To: Grant Coady <lkml@dodo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc5 randconfig kernel build errors
Date: Wed, 3 Aug 2005 13:20:50 +0200 [thread overview]
Message-ID: <20050803112050.GL4029@stusta.de> (raw)
In-Reply-To: <1651f199ie23tv14qv8jnnc53m97qdk1uh@4ax.com>
On Wed, Aug 03, 2005 at 07:58:02PM +1000, Grant Coady wrote:
> On Tue, 02 Aug 2005 22:58:59 +1000, Grant Coady <lkml@dodo.com.au> wrote:
>
> >Greetings,
> >
> >Preliminary results, better sample (some hundreds) in a day or so.
>
> After 300 random builds, add one more error:
> drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this function)
> drivers/acpi/osl.c:61:10: empty file name in #include
Please exclude builds with CONFIG_STANDALONE=n.
And please don't send every new error you are finding to this list.
As I've already said generating the errors is the the easy part -
analyzing them is the real work.
It would be best if you would do this yourself and send specific bug
reports (or even patches) for the problems you've find.
If you want to publish the errors you've found, send a pointer to a
location where it is available _once_ and update the information there.
This is e.g. how Jan Dittmer is doing it with his very valuable cross
compile site [1] - he doesn't send daily emails but if I want to know
the information I can always find it there.
> Cheers,
> Grant.
cu
Adrian
[1] http://l4x.org/k/
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-03 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 12:58 2.6.13-rc5 randconfig kernel build errors Grant Coady
2005-08-03 9:58 ` Grant Coady
2005-08-03 11:20 ` Adrian Bunk [this message]
2005-08-03 15:41 ` Grant Coady
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=20050803112050.GL4029@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dodo.com.au \
/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