From: Dan Christian <Daniel.A.Christian@NASA.gov>
To: "John Appleby" <john@dnsworld.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 SMP module unresolved symbols
Date: Wed, 4 Jun 2003 11:06:01 -0700 [thread overview]
Message-ID: <200306041106.01316.Daniel.A.Christian@NASA.gov> (raw)
In-Reply-To: <434747C01D5AC443809D5FC5405011314BEC@bobcat.unickz.com>
On Wednesday 04 June 2003 09:20, John Appleby wrote:
> > No, I didn't do "make mrproper". I'll try that.
> >
> > It used to be that it wasn't needed and it liked to blow away
> > .config (an extreme mis-feature if I ever saw one).
>
> Not a mis-feature for those making diffs on the kernel tree and not
> wanting their .config to be included erroneously :)
>
> Regards,
>
> John
"make mrproper" fixes it.
For the record, I think this stinks!
"make mrproper" should be an expert only utility because it does blow
away valuable configuration information (a painfull lesson that can
only be learned "the hard way", since the README neglicts to mention
this). For that matter, the README makes it look like creating a
config from scratch (all 1500+ options) is no big deal!
"make clean; make dep" should have been enough for any config changes
(it used to be in the past).
-Dan
next parent reply other threads:[~2003-06-04 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <434747C01D5AC443809D5FC5405011314BEC@bobcat.unickz.com>
2003-06-04 18:06 ` Dan Christian [this message]
2003-06-04 19:36 ` 2.4.21-rc7 SMP module unresolved symbols Samuel Flory
2003-06-04 20:00 ` Richard B. Johnson
2003-06-04 21:33 ` Alan Cox
2003-06-04 0:28 Dan Christian
2003-06-04 0:32 ` Marc-Christian Petersen
2003-06-04 16:00 ` Dan Christian
2003-06-04 5:30 ` Keith Owens
2003-06-04 8:31 ` J.A. Magallon
2003-06-04 9:34 ` Clemens Schwaighofer
2003-06-04 15:57 ` Dan Christian
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=200306041106.01316.Daniel.A.Christian@NASA.gov \
--to=daniel.a.christian@nasa.gov \
--cc=john@dnsworld.co.uk \
--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