From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7154] New: Local uClibc config file gets overwritten using make uclibc-update-config
Date: Tue, 3 Jun 2014 12:36:19 +0000 (UTC) [thread overview]
Message-ID: <bug-7154-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7154
Summary: Local uClibc config file gets overwritten using make
uclibc-update-config
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Windows
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: oliver.kasten at trsystems.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I've defined an external place for the uClibc config file using
BR_UCLIBC_CONFIG. After editing the configuration with make uclibc-menuconfig I
want to copy the edited config file with make uclibc-update-config to the
external place.
It seems that before copying the config file to the external place, it gets
re-configured using the UCLIBC_CONFIGURE_CMDS, which overwrites the local
config file with the external file.
For me deleting the .stamp_configured file in the uclibc-menuconfig entry of
the makefile seems not to be a good idea.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-06-03 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 12:36 bugzilla at busybox.net [this message]
2014-06-10 13:22 ` [Buildroot] [Bug 7154] Local uClibc config file gets overwritten using make uclibc-update-config bugzilla at busybox.net
2014-06-10 13:56 ` bugzilla at busybox.net
2014-06-22 13:52 ` bugzilla at busybox.net
2014-06-22 13:53 ` bugzilla at busybox.net
2014-07-30 20:03 ` bugzilla at busybox.net
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=bug-7154-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.