From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH 0/4] support building from read-only source tree
Date: Sun, 26 May 2013 16:45:40 +0200 [thread overview]
Message-ID: <20130526144540.GA3380@free.fr> (raw)
In-Reply-To: <1340031743-29694-1-git-send-email-ntl@pobox.com>
Nathan, All,
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.
>
> This works fine when the source file has write permissions; this is
> preserved in the destination copy. This is the behavior in the common
> case of running from a git repository or a release tarball.
>
> However, when the source file is read-only, the destination copy is
> also not writable and such fixups fail. This occurs when the the
> Buildroot source tree is being hosted in a Perforce repository.
> Perforce uses local file permissions to track whether a file is being
> edited and checks out all regular files read-only by design.
>
> The following changes were enough to get qemu_mips_malta_defconfig to
> build and run successfully. I submit these patches for discussion and
> illustration of the effort required to support this use case.
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.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-05-26 14:45 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 ` Yann E. MORIN [this message]
2013-05-26 16:36 ` [Buildroot] [RFC/PATCH 0/4] support building from read-only source tree Yann E. MORIN
2013-05-30 20:36 ` Nathan Lynch
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=20130526144540.GA3380@free.fr \
--to=yann.morin.1998@free.fr \
--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