Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] package/uClibc: ensure .oldconfig is writable
Date: Fri, 15 Nov 2013 09:18:33 +0100	[thread overview]
Message-ID: <20131115091833.4b685ebe@skate> (raw)
In-Reply-To: <9f08675878a925c9850b26ced36ed5e1edf53c9b.1384454667.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Thu, 14 Nov 2013 19:46:58 +0100, Yann E. MORIN wrote:

> source dir is), the sed fixups to .oldconfig fail.

You mention .oldconfig here (and in the commit title)

> -	cp -f $(UCLIBC_CONFIG_FILE) $(@D)/.config
> +	$(INSTALL) -m 0644 $(UCLIBC_CONFIG_FILE) $(@D)/.config

but it's actually .config that is taken care of :)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-15  8:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 18:46 [Buildroot] [pull request v2] Pull request for branch yem/patchwork Yann E. MORIN
2013-11-14 18:46 ` [Buildroot] [PATCH 1/5] target: ensure target/ dir is writable Yann E. MORIN
2014-01-28  0:31   ` Danomi Manchego
2014-01-28 18:25     ` Yann E. MORIN
2014-01-28 18:37       ` Danomi Manchego
2013-11-14 18:46 ` [Buildroot] [PATCH 2/5] busybox: ensure $(BUSYBOX_BUILD_CONFIG) " Yann E. MORIN
2013-11-14 18:46 ` [Buildroot] [PATCH 3/5] linux: ensure buildroot_defconfig " Yann E. MORIN
2013-11-14 19:24   ` Danomi Manchego
2013-11-14 18:46 ` [Buildroot] [PATCH 4/5] package/uClibc: ensure .oldconfig " Yann E. MORIN
2013-11-15  8:18   ` Thomas Petazzoni [this message]
2013-11-14 18:46 ` [Buildroot] [PATCH 5/5] fs: ensure $(TARGET_DIR_WARNING_FILE) " 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=20131115091833.4b685ebe@skate \
    --to=thomas.petazzoni@free-electrons.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