mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: displaying kbuild dependancies ...
Date: Sat, 11 Sep 2004 22:25:48 +0200	[thread overview]
Message-ID: <20040911202548.GA31680@MAIL.13thfloor.at> (raw)


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 ...

so, now the question:

is there a magic option, simple procedure, or just
quick and dirty hack to get a list or some kind 
of dependancy graph from the kbuild system?

TIA,
Herbert



             reply	other threads:[~2004-09-11 20:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 20:25 Herbert Poetzl [this message]
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

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=20040911202548.GA31680@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.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®