From: Adrian Bunk <bunk@stusta.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: George Kasica <georgek@netwrx1.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem compiling 2.6.12
Date: Wed, 22 Jun 2005 18:44:36 +0200 [thread overview]
Message-ID: <20050622164436.GI3705@stusta.de> (raw)
In-Reply-To: <9a874849050622085975b67c06@mail.gmail.com>
On Wed, Jun 22, 2005 at 05:59:45PM +0200, Jesper Juhl wrote:
>
> Don't use a 2.4.x config as the basis for a 2.6.x kernel .
> Build your first 2.6.x kernel config using "make menuconfig", "make
> config", make xconfig" or similar, /then/ you can use that config in
> the future as a base for other 2.6.x kernels with "make oldconfig".
First of all, this shouldn't result in problems like the one he
reported (see my other mail).
And I'm surprised you are saying this. I'd have expected that running
"make oldconfig" with a 2.4 kernel should give him a working
configuration.
Can you explain where you'd expect problems so that we can fix them?
> Jesper Juhl <jesper.juhl@gmail.com>
cu
Adrian
--
"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-06-22 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 15:28 Problem compiling 2.6.12 George Kasica
2005-06-22 15:59 ` Jesper Juhl
2005-06-22 16:44 ` Adrian Bunk [this message]
2005-06-22 19:15 ` George Kasica
2005-06-22 19:26 ` Jesper Juhl
2005-06-22 19:14 ` George Kasica
2005-06-22 19:45 ` Richard B. Johnson
2005-06-22 16:42 ` Adrian Bunk
2005-06-22 19:22 ` George Kasica
2005-06-22 21:33 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-06-22 19:37 Nick Warne
2005-06-22 21:30 ` Adrian Bunk
2005-06-22 21:53 ` Nick Warne
2005-06-23 9:53 ` Adrian Bunk
2005-06-23 11:08 ` Nix
2005-06-23 21:26 Sid Boyce
[not found] <Pine.LNX.4.62.0506240856460.10920@eagle.netwrx1.com>
[not found] ` <42BC1C43.3040505@blueyonder.co.uk>
[not found] ` <Pine.LNX.4.62.0506241258500.20958@eagle.netwrx1.com>
[not found] ` <42BC9FF1.1010400@blueyonder.co.uk>
[not found] ` <5nerb117olj7kahv0k8b1vss382ini6bfr@4ax.com>
2005-06-26 0:39 ` Sid Boyce
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=20050622164436.GI3705@stusta.de \
--to=bunk@stusta.de \
--cc=georgek@netwrx1.com \
--cc=jesper.juhl@gmail.com \
--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