From: Randy Dunlap <rdunlap@xenotime.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: error when using KCONFIG_ALLCONFIG?
Date: Wed, 29 Apr 2009 16:55:48 -0700 [thread overview]
Message-ID: <49F8E904.3080601@xenotime.net> (raw)
In-Reply-To: <20090429234911.GA1922@uranus.ravnborg.org>
Sam Ravnborg wrote:
> On Wed, Apr 29, 2009 at 03:38:36PM -0700, Randy Dunlap wrote:
>> Hi,
>>
>> I often use
>> make KCONFIG_ALLCONFIG=filename allnoconfig
>>
>> and it works fine. However, when I use O= with that:
>>
>> make O=xx64 KCONFIG_ALLCONFIG=filename allnoconfig
>>
>> I get an xx64/.config file that is the same as
>>
>> make O=xx64 allnoconfig
>>
>> I.e., the KCONFIG_ALLCONFIG=filename part was ignored.
>>
>> Is this new? expected? known?
> I dunno if it is new but it is not expected.
> Can you try if it help to move 'filename' to output directory.
make O=xx64 KCONFIG_ALLCONFIG=xx64/filename allnoconfig
gives the same result as 'make allnoconfig'.
---
next prev parent reply other threads:[~2009-04-29 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 22:38 error when using KCONFIG_ALLCONFIG? Randy Dunlap
2009-04-29 23:49 ` Sam Ravnborg
2009-04-29 23:55 ` Randy Dunlap [this message]
2009-04-30 20:25 ` Randy Dunlap
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=49F8E904.3080601@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kbuild@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