From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: John Linn <John.Linn@xilinx.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kconfig debug help
Date: Tue, 05 Aug 2008 18:48:48 -0400 [thread overview]
Message-ID: <1217976528.2328.54.camel@localhost.localdomain> (raw)
In-Reply-To: <20080805213759.96642158806D@mail101-wa4.bigfish.com>
On Tue, 2008-08-05 at 15:37 -0600, John Linn wrote:
> I’m trying to debug some Kconfig problems and am looking for a way to
> get more debug output.
>
>
>
> I have used KBUILD_VERBOSE=1 on the command line and it didn’t help
> much.
>
>
>
> I’m seeing an issue with creating a new defconfig file for a board. I
> get the .config created, then copy it to a defconfig, and then it
> doesn’t do anything when I run make with the defconfig file.
Yeah, I hit that myself this weekend. It's a bug in the Kconfig area.
It's 1/2 fixed in the latest Linus and powerpc trees.
josh
next prev parent reply other threads:[~2008-08-05 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 21:37 Kconfig debug help John Linn
2008-08-05 22:48 ` Josh Boyer [this message]
2008-08-05 22:50 ` John Linn
2008-08-06 9:46 ` Geert Uytterhoeven
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=1217976528.2328.54.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=John.Linn@xilinx.com \
--cc=linuxppc-dev@ozlabs.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