From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Declare SED Makefile instead of package/Makefile.in so it exists globally.
Date: Sat, 27 Feb 2016 23:00:46 +0100 [thread overview]
Message-ID: <87y4a5rey9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56D1A1E6.7020601@mind.be> (Arnout Vandecappelle's message of "Sat, 27 Feb 2016 14:17:26 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Arnout, what do you think? In addition, I think it would be good t In
>> addition, I think it would be good to In addition, I think it would
>> be good to o
> I agree we should go for (1).
Yes, I also think this is the sanest / simplest thing to do.
> However, this doesn't completely stop the 'make menuconfig savedefconfig': once
> a .config file exists, you can still do that. But it could have some funky side
> effects (not that I can think of any right away, but it feels a bit iffy). So I
> think it would be good to enforce that all the noconfig_targets can only be
> called on their own on the command line. This would block completely silly
> things like 'make menuconfig defconfig' (it would also block potentially valid
> things like 'make foo_defconfig menuconfig', but I think adding an extra '&&
> make' in the middle of that is not so painful).
No, that seems ok (as long as it is clear from the error message that
you need to do so).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-02-27 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 10:26 [Buildroot] $(SED) not defined if 'make menuconfig savedefconfig' Alvaro Gamez
2015-06-15 13:37 ` Thomas Petazzoni
2015-06-15 14:20 ` rdkehn at yahoo.com
2015-06-16 7:58 ` Alvaro Gamez
2016-02-16 11:46 ` Alvaro Gamez
2016-02-16 15:10 ` Thomas Petazzoni
2016-02-16 15:15 ` [Buildroot] [PATCH 1/1] Declare SED Makefile instead of package/Makefile.in so it exists globally Alvaro G. M
2016-02-16 20:35 ` Thomas Petazzoni
2016-02-16 22:35 ` Arnout Vandecappelle
2016-02-17 8:22 ` Alvaro Gamez
2016-02-17 8:47 ` Thomas Petazzoni
2016-02-27 13:17 ` Arnout Vandecappelle
2016-02-27 22:00 ` Peter Korsgaard [this message]
2016-02-28 7:43 ` Alvaro Gamez
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=87y4a5rey9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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