From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2] busybox/uclibc: copy config file from configure step
Date: Thu, 13 Feb 2014 12:34:43 +0100 [thread overview]
Message-ID: <patchbomb.1392291283@argentina> (raw)
This patch series changes busybox and uclibc to copy the .config file from
the configure step, and not earlier (patch or extract step). This fixes the
usage of OVERRIDE_SRCDIR with these packages.
This was reported for busybox in bug #5030.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
package/busybox/busybox.mk | 4 +---
package/uclibc/uclibc.mk | 3 +--
2 files changed, 2 insertions(+), 5 deletions(-)
next reply other threads:[~2014-02-13 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 11:34 Thomas De Schampheleire [this message]
2014-02-13 11:34 ` [Buildroot] [PATCH 1 of 2] busybox: copy config file from configure iso extract step Thomas De Schampheleire
2014-02-13 11:34 ` [Buildroot] [PATCH 2 of 2] uclibc: copy config file from configure iso patch step Thomas De Schampheleire
2014-02-14 20:32 ` [Buildroot] [PATCH 0 of 2] busybox/uclibc: copy config file from configure step Thomas De Schampheleire
2014-02-14 20:37 ` Peter Korsgaard
2014-02-14 20:40 ` Thomas De Schampheleire
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=patchbomb.1392291283@argentina \
--to=patrickdepinguin@gmail.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