From: Nathan Lynch <ntl@pobox.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH 0/4] support building from read-only source tree
Date: Thu, 30 May 2013 15:36:37 -0500 [thread overview]
Message-ID: <1369946197.13828.33.camel@doorstop.aus.2wire.com> (raw)
In-Reply-To: <20130526163633.GB3380@free.fr>
On Sun, 2013-05-26 at 18:36 +0200, Yann E. MORIN wrote:
> Nathan, All,
>
> On 2013-05-26 16:45 +0200, Yann E. MORIN spake thusly:
> > On 2012-06-18 10:02 -0500, Nathan Lynch spake thusly:
> > > There are several places in Buildroot where files are copied from the
> > > source tree to the output directory and then modified. The most
> > > obvious case is copying a .config or equivalent to the build
> > > directory and then modifying it with sed, as with uClibc or busybox.
> >
> > Unfortunately, those patches mostly no longer apply, since there have
> > been some code churn (reoridering) in the meantime.
> >
> > I'll take whatever I can, and adapt the remaining.
>
> I've added them to my patchwork branch:
> https://www.gitorious.org/buildroot/buildroot/commits/yem-patchwork-fixes
>
> Thank you!
Thank you for picking these up. I haven't been sufficiently motivated
to pursue these (obviously); hopefully they will be useful to others.
prev parent reply other threads:[~2013-05-30 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 15:02 [Buildroot] [RFC/PATCH 0/4] support building from read-only source tree Nathan Lynch
2012-06-18 15:02 ` [Buildroot] [RFC/PATCH 1/4] uClibc: ensure .oldconfig is writable Nathan Lynch
2012-06-18 15:02 ` [Buildroot] [RFC/PATCH 2/4] ensure target fs " Nathan Lynch
2012-06-20 23:12 ` Arnout Vandecappelle
2012-06-18 15:02 ` [Buildroot] [RFC/PATCH 3/4] busybox: ensure $(BUSYBOX_BUILD_CONFIG) " Nathan Lynch
2012-06-20 23:13 ` Arnout Vandecappelle
2012-06-18 15:02 ` [Buildroot] [RFC/PATCH 4/4] linux: ensure buildroot_defconfig " Nathan Lynch
2013-05-26 14:45 ` [Buildroot] [RFC/PATCH 0/4] support building from read-only source tree Yann E. MORIN
2013-05-26 16:36 ` Yann E. MORIN
2013-05-30 20:36 ` Nathan Lynch [this message]
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=1369946197.13828.33.camel@doorstop.aus.2wire.com \
--to=ntl@pobox.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