linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: miller@techsource.com, linux-kernel@vger.kernel.org
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Tue, 22 Apr 2003 13:51:39 -0700	[thread overview]
Message-ID: <20030422135139.0a1ab3cd.rddunlap@osdl.org> (raw)
In-Reply-To: <200304222041.h3MKfILq027562@turing-police.cc.vt.edu>

On Tue, 22 Apr 2003 16:41:18 -0400 Valdis.Kletnieks@vt.edu wrote:

| On Tue, 22 Apr 2003 16:49:03 EDT, Timothy Miller <miller@techsource.com>  said:
| > Is anyone else able to build 2.5.68 with allyesconfig?
| > 
| > I'm using RH7.2, so the first thing I did was edit the main Makefile to 
| > replace gcc with "gcc3" (3.0.4).  Maybe the compiler is STILL my 
| >
| 
| 1) I think the 3.0.4 compiler had some issues - 3.2.2 may be a better idea.
| 
| 2) allyesconfig is probably NOT able to build an actual kernel that will
| work - in particular, there are a number of pairs/sets of drivers that are
| mutually exclusive for a given device. And as you noticed, allyesconfig
| will try to build stuff that's known to be b0rken.
| 
| 3) Even if it works, it will be a huge kernel with lots of stuff you almost
| certainly don't need (got an ISDN card? I didn't think so ;).  You would more
| likely want to customize the kernel for what you need, or at least consider
| using 'allmodconfig' so you can insmod the parts you need and skip the rest.

After you weed out the 50 or so drivers that won't compile (disable them),
you'll end up with a kernel that is way to big to boot.
I did this about 2 months ago and posted the results to lkml.

But it's a good build-only tool.

--
~Randy

  reply	other threads:[~2003-04-22 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:49 Can one build 2.5.68 with allyesconfig? Timothy Miller
2003-04-22 20:41 ` Valdis.Kletnieks
2003-04-22 20:51   ` Randy.Dunlap [this message]
2003-04-22 21:04   ` Timothy Miller
2003-04-22 20:57     ` Valdis.Kletnieks
2003-04-22 22:25       ` Timothy Miller
2003-04-22 21:06 ` Richard B. Johnson
2003-04-23 19:52   ` John Cherry
2003-04-23 20:48     ` Jörn Engel
2003-04-24  0:01       ` John Cherry
2003-04-24  9:26         ` Jörn Engel
2003-04-22 21:08 ` Sam Ravnborg
2003-04-22 21:19   ` Randy.Dunlap
2003-04-23 11:58 ` Jörn Engel

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=20030422135139.0a1ab3cd.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    /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;
as well as URLs for NNTP newsgroup(s).