public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Tue, 15 Jan 2002 02:07:58 +0000	[thread overview]
Message-ID: <20020115020758.GA59418@compsoc.man.ac.uk> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com> <20020115013954.GB3814@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20020115013954.GB3814@cpe-24-221-152-185.az.sprintbbd.net>

On Mon, Jan 14, 2002 at 06:39:54PM -0700, Tom Rini wrote:

> Wrong.  She needs to compile a new module for her kernel.  What might be
> useful is some automagic tool that will find the vendor-provided kernel
> source tree and config (which is usually /boot/config-`uname -r`, but
> still findable anyhow)

autoconf code already exists for this, it's a non-problem. Note they must use
the config in the header file of the vendor-provided kernel source tree, not
/boot/config-`uname -r`

There are two cases:

1) the vendor source tree is installed and set up with the right config -> use header file

2) it's installed and the config has changed. -> use header file

I don't see a point in ever looking at /boot/config-`uname -r` instead of
the source tree, given that we must compile against a tree configured like the
eventual running kernel anyway.

regards
john

-- 
"Now why did you have to go and mess up the child's head, so you can get another gold waterbed ?
 You fake-hair contact-wearing liposuction carnival exhibit, listen to my rhyme ..."

  reply	other threads:[~2002-01-15  3:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 21:59 Penelope builds a kernel Eric S. Raymond
2002-01-14 22:24 ` Jeff Garzik
2002-01-14 22:28 ` Lars Marowsky-Bree
2002-01-14 22:32 ` Davide Libenzi
2002-01-14 22:32 ` Chris Friesen
2002-01-14 22:35 ` Benjamin LaHaise
2002-01-14 22:38   ` Eric S. Raymond
2002-01-14 23:00     ` Benjamin LaHaise
2002-01-14 23:05       ` Eric S. Raymond
2002-01-14 23:38         ` Benjamin LaHaise
2002-01-15  1:53           ` Eric S. Raymond
2002-01-15  2:36             ` Benjamin LaHaise
2002-01-15 11:53               ` Matthias Andree
2002-01-15 22:32             ` James Antill
2002-01-15 22:28               ` Eric S. Raymond
2002-01-16  1:29                 ` Alan Cox
2002-01-15 23:00               ` Diego Calleja
2002-01-14 22:37 ` Bruce Harada
2002-01-15  0:56   ` Thomas Duffy
2002-02-01 20:46   ` Pavel Zaitsev
2002-01-14 22:44 ` Richard Gooch
2002-01-14 22:45   ` Eric S. Raymond
2002-01-14 23:15     ` Richard Gooch
2002-01-15 15:53     ` salvador
2002-01-14 23:08 ` Chris Ricker
2002-01-14 23:14 ` Tom Gilbert
2002-01-15  0:50 ` Nathan Walp
2002-01-15  1:24   ` John Levon
2002-01-15  1:39 ` Tom Rini
2002-01-15  2:07   ` John Levon [this message]
2002-01-15  3:59     ` Tom Rini
2002-01-15 13:28 ` David Woodhouse
2002-01-15 19:53   ` Ingo Oeser
2002-01-15 20:37   ` David Woodhouse
2002-01-15 21:00 ` Matthew M
2002-01-16 21:31 ` Felix von Leitner
     [not found] <d7.11a4a260.2974c807@aol.com>
2002-01-14 23:51 ` Jeff Garzik

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=20020115020758.GA59418@compsoc.man.ac.uk \
    --to=movement@marcelothewonderpenguin.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