mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: displaying kbuild dependancies ...
Date: Tue, 14 Sep 2004 17:37:00 +0200	[thread overview]
Message-ID: <20040914153700.GA2683@MAIL.13thfloor.at> (raw)
In-Reply-To: <20040914082841.4bde2c77.rddunlap@osdl.org>

On Tue, Sep 14, 2004 at 08:28:41AM -0700, Randy.Dunlap wrote:
> On Sun, 12 Sep 2004 23:30:34 +0200 Herbert Poetzl wrote:
> 
> | On Sat, Sep 11, 2004 at 11:39:31PM +0200, Sam Ravnborg wrote:
> | > On Sat, Sep 11, 2004 at 10:25:48PM +0200, Herbert Poetzl wrote:
> | > > 
> | > > Hi Sam!
> | > > 
> | > > first, thanks for the kbuild stuff and all the 
> | > > time spent on that ... I really love it
> | > > 
> | > > 
> | > > from time to time I encounter some issue which
> | > > usually keeps me busy for a while, and I think
> | > > there probably is a simpler solution to that ...
> | > > 
> | > > the procedure:
> | > > 
> | > > I'm configuring a 2.6.X-rcY-bkZ kernel for testing
> | > > with QEMU, which in my setup basically requires
> | > > some QEMU specific settings, I usually turn on/off
> | > > by just editing the .config file by hand, and then
> | > > invoking 'make oldconfig' ...
> | > > 
> | > > to keep the possibility for error low, I usually
> | > > just remove the entries in question, and oldconfig
> | > > will ask me the relevant question, leading to a
> | > > nice config adapted to my purposes ...
> | > > 
> | > > the issue:
> | > > 
> | > > sometimes a dependancy doesn't allow me to remove
> | > > a config option, I absolutely have to remove for
> | > > my setup, like the VGA_CONSOLE, and then the hunt
> | > > for the option 'requiring' that one unconditinally
> | > > beginns ...
> | > > 
> | > > usually I start with grep and end with trial and
> | > > error, until I find the malicious dependancy ...
> | > 
> | > The only option today is to turn on the debug option
> | > in 'make xconfig'.
> | 
> | hmm, so no luck for the typical console user  :(
> | 
> | > I have been looking inot something better for menuconfig
> | > but frankly kconfig is not where I feel most comfortable.
> | 
> | it would be sufficient to be able to turn on some
> | debug output, which says 'foo selected from bla'
> | or 'foo disabled, requires bla and whatnot' ...
> 
> There are some menuconfig patches in -mm (from Yuval Turgeman)
> that add a search option (using '/') to menuconfig.
> E.g., enter / + USB_STORAGE and you can see everywhere
> that USB_STORAGE is used.... and that it SELECTs SCSI.
> To see only the USB_STORAGE kconfig entry, use a regex:
> ^USB_STORAGE$

sounds great! 
will investigate this ...

> IIRC, Yuval is considering how to enhance this feature.

thanks for the info,
Herbert

> --
> ~Randy

      reply	other threads:[~2004-09-14 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 20:25 Herbert Poetzl
2004-09-11 21:39 ` Sam Ravnborg
2004-09-12 21:30   ` Herbert Poetzl
2004-09-14 15:28     ` Randy.Dunlap
2004-09-14 15:37       ` Herbert Poetzl [this message]

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=20040914153700.GA2683@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®