linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Tue, 22 Apr 2003 16:57:37 -0400	[thread overview]
Message-ID: <200304222057.h3MKvbLq005110@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 22 Apr 2003 17:04:34 EDT." <3EA5AE62.1040706@techsource.com>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

On Tue, 22 Apr 2003 17:04:34 EDT, Timothy Miller said:

> Great.  Why do I have a feeling that installing it will bork my 
> workstation?  Not to say that it can't be done but that I will probably 
> screw it up.  I'm sure that Red Hat (7.2) has some dependencies on there 
> being 2.96 installed.  Any suggestions on how I might deal with this 
> problem?

Well...

> I'm not actually going to run the kernel.

Then the use of 3.0.2 won't matter..

> I'm trying to do an allyesconfig kernel so that I can get all printk 
> format strings.

'make -k' should suffice there.  I assume you're grovelling them out of
the .o files?  Otherwise, just grepping the *.c should be OK.

Also, note that you probably want to *also* do an 'allmodconfig' just in
case there's printk inside a #ifdef MODULE....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2003-04-22 20:45 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
2003-04-22 21:04   ` Timothy Miller
2003-04-22 20:57     ` Valdis.Kletnieks [this message]
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=200304222057.h3MKvbLq005110@turing-police.cc.vt.edu \
    --to=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).