From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10386] Add an option to put all compiled executables that show up on target/ in staging/ as well
Date: Mon, 30 Sep 2019 11:14:54 +0000 [thread overview]
Message-ID: <bug-10386-163-SNhoESdneR@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10386-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10386
Carlos Santos <unixmania@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at buildroot.uclibc |unixmania at gmail.com
|.org |
--- Comment #1 from Carlos Santos <unixmania@gmail.com> ---
This bug has been dormant for a long time. It look like a feature request
rather
than a bug but anyway it sounds valid. The proposed solution, however is hard
to
implement.
Since Buildroot 2018.05 the root filesystem image is generated from a copy of
TARGER_DIR, so we can move the strpping from target-finalize to the fakeroot
script. This way we strip binaries only in the intermediary copy.
I will submit a patch with this change for review.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-30 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 17:08 [Buildroot] [Bug 10386] New: Add an option to put all compiled executables that show up on target/ in staging/ as well bugzilla at busybox.net
2019-09-30 11:14 ` bugzilla at busybox.net [this message]
2020-04-13 23:51 ` [Buildroot] [Bug 10386] " 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-10386-163-SNhoESdneR@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox