From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] busybox: ensure $(BUSYBOX_BUILD_CONFIG) is writable
Date: Tue, 12 Nov 2013 18:42:47 +0100 [thread overview]
Message-ID: <20131112174247.GA3434@free.fr> (raw)
In-Reply-To: <CANxTyt5qCLXrOCnp5hrxwTkzfoH3DORs6uoDiBr5Jr1w3+0R2A@mail.gmail.com>
Danomi, All,
On 2013-11-11 15:22 -0500, Danomi Manchego spake thusly:
> On Mon, Nov 11, 2013 at 12:45 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > From: Nathan Lynch <ntl@pobox.com>
> >
> > If $(BUSYBOX_CONFIG_FILE) is read-only (eg. because Buildroot's
> > source dir is), the sed fixups to $(BUSYBOX_BUILD_CONFIG) fail.
>
> These share the same issue:
>
> - linux.mk: $(KERNEL_ARCH_PATH)/configs/buildroot_defconfig
> - uclibc,mk: $(UCLIBC_DIR)/.oldconfig
Indeed, I'll add them to the series. Thanks! :-)
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-11-12 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:45 [Buildroot] [pull request] Pull request for branch yem/patchwork Yann E. MORIN
2013-11-11 17:45 ` [Buildroot] [PATCH 1/2] target: ensure target/ dir is writable Yann E. MORIN
2013-11-11 17:45 ` [Buildroot] [PATCH 2/2] busybox: ensure $(BUSYBOX_BUILD_CONFIG) " Yann E. MORIN
2013-11-11 20:22 ` Danomi Manchego
2013-11-12 17:42 ` Yann E. MORIN [this message]
2013-11-12 17:54 ` Danomi Manchego
2013-11-12 18:26 ` Yann E. MORIN
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=20131112174247.GA3434@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.