From: David Greaves <david@dgreaves.com>
To: gcoady@gmail.com
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Mon, 27 Feb 2006 12:56:07 +0000 [thread overview]
Message-ID: <4402F6E7.3050500@dgreaves.com> (raw)
In-Reply-To: <336402hq8014pc1cg8169f8tumhj302vho@4ax.com>
Grant Coady wrote:
>On Sun, 26 Feb 2006 17:21:17 +0100, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
>
>>Hi everyone,
>>
>>I just sat down and build 100 kernels (2.6.16-rc4-mm2 kernels to be exact)
>>
>> 95 kernels were build with 'make randconfig'.
>>
>>
>>That was an interresting experience.
>>
>>
>
>Welcome to the club ;) I gave up make randconfig months ago as
>there's simply too much noise in there... There are same errors
>popping up for months now without resolution, and I lack experience
>to fix most things I see -- asked akpm once but not grok Andrew's
>response (months ago).
>
>
How about introducing an 'overlay' config that is introduced after
randconfig runs?
That gives you the ability to, for example, always set
CONFIG_EMBEDDED=n
Then you can progressivley eliminate some known issues (which is not
what you're trying to find anyway).
David
--
next prev parent reply other threads:[~2006-02-27 12:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 16:21 Building 100 kernels; we suck at dependencies and drown in warnings Jesper Juhl
2006-02-26 16:31 ` Jesper Juhl
2006-02-26 16:35 ` Jesper Juhl
2006-02-26 19:31 ` Dave Jones
2006-02-26 19:43 ` Jesper Juhl
2006-02-26 20:11 ` Jesper Juhl
2006-02-26 23:45 ` Nigel Cunningham
2006-02-27 2:02 ` Pavel Machek
2006-02-26 19:30 ` Dave Jones
2006-02-26 17:00 ` Adrian Bunk
2006-02-26 17:29 ` Jesper Juhl
2006-02-26 17:41 ` Adrian Bunk
2006-02-26 18:08 ` Jesper Juhl
2006-02-26 17:38 ` Jesper Juhl
2006-02-26 18:21 ` Diego Calleja
2006-02-26 18:45 ` Jesper Juhl
2006-02-26 19:03 ` Diego Calleja
2006-02-26 20:42 ` Lee Revell
2006-02-26 20:44 ` Jesper Juhl
2006-02-26 21:46 ` Nix
2006-02-26 21:49 ` Jesper Juhl
2006-02-26 21:53 ` Lee Revell
2006-02-26 21:56 ` Jesper Juhl
2006-02-26 22:08 ` Lee Revell
2006-02-26 22:12 ` Jesper Juhl
2006-02-27 17:25 ` Stephen Hemminger
2006-02-26 22:14 ` Al Viro
2006-02-26 22:32 ` Nix
2006-02-26 22:50 ` Lee Revell
2006-02-26 21:14 ` Grant Coady
2006-02-27 12:56 ` David Greaves [this message]
2006-02-28 10:30 ` Roman Zippel
2006-02-26 22:43 ` Sam Ravnborg
2006-03-02 20:25 ` Jesper Juhl
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=4402F6E7.3050500@dgreaves.com \
--to=david@dgreaves.com \
--cc=akpm@osdl.org \
--cc=gcoady@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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