public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: George Kasica <georgek@netwrx1.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem compiling 2.6.12
Date: Wed, 22 Jun 2005 21:26:37 +0200	[thread overview]
Message-ID: <9a87484905062212264e82d770@mail.gmail.com> (raw)
In-Reply-To: <20050622164436.GI3705@stusta.de>

On 6/22/05, Adrian Bunk <bunk@stusta.de> wrote:
> 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?
> 
It's been ages since I personally moved to 2.6, but around the time
when I made the switch I fed several 2.4 configs to oldconfig and the
resulting 2.6 kernels either didn't build properly or they build but
were broken in strange ways. Redoing the 2.6 configs from scratch
always fixed the problems back then. I also encountered similar
reports from people on IRC. Things may have improved since then, but
then again maybe they have not.. I'll see if I can dig out a few of my
old 2.4 configs and retest if there are still issues.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2005-06-22 19:27 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
2005-06-22 19:15     ` George Kasica
2005-06-22 19:26     ` Jesper Juhl [this message]
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=9a87484905062212264e82d770@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=bunk@stusta.de \
    --cc=georgek@netwrx1.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