From: Andi Kleen <andi@firstfloor.org>
To: linux-kbuild@vger.kernel.org
Subject: ifdef CONFIG in top level makefile
Date: Mon, 10 Feb 2014 06:54:46 +0100 [thread overview]
Message-ID: <20140210055446.GQ11821@two.firstfloor.org> (raw)
Here's one interesting problem I hit with LTO:
I added some ifdef CONFIG_.... checks early in the top level Makefile.
But I noticed that when a config is first generated these CONFIGs
seem to be ignored, it's only read later. I assume that is because
the Makefile is no re-parsed after the config is fully set up.
Correct theory? If yes is there a workaround for this?
I assume this could hit other ifdefs in that Makefile too.
Thanks.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
reply other threads:[~2014-02-10 5:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140210055446.GQ11821@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kbuild@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