From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 5 v2] stripping: use findfileclauses utility function
Date: Fri, 18 Nov 2011 00:06:03 +0000 [thread overview]
Message-ID: <201111180006.04412.arnout@mind.be> (raw)
In-Reply-To: <26239e4561037c19ccfc.1321557991@devws108>
On Thursday 17 November 2011 19:41:56 Thomas De Schampheleire wrote:
> # HG changeset patch
> # User Thomas De Schampheleire <thomas.de_schampheleire@alcatel-lucent.com>
> # Date 1318576710 -7200
> # Node ID 26239e4561037c19ccfc7ac7ea216d36a6a8e87e
> # Parent b6579582d02dd802adca94e2b38972cc19cd8b76
> stripping: use findfileclauses utility function
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
I think this patch is redundant: it doesn't simplify anything, nobody would
want to apply or revert it individually.
Regards,
Arnout
>
> ---
> Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> --- a/Makefile
> +++ b/Makefile
> @@ -454,7 +454,7 @@ endif
> ifeq ($(BR2_PACKAGE_PYTHON_PYC_ONLY),y)
> find $(TARGET_DIR)/usr/lib/ -name '*.py' -print0 | xargs -0 rm -f
> endif
> - find $(TARGET_DIR) -type f -perm +111 '!' -name 'libthread_db*.so*' | \
> + find $(TARGET_DIR) -type f -perm +111 '!' $(call findfileclauses,libthread_db*.so*) | \
> xargs $(STRIPCMD) 2>/dev/null || true
> find $(TARGET_DIR)/lib/modules -type f -name '*.ko' | \
> xargs -r $(KSTRIPCMD) || true
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-11-18 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 19:41 [Buildroot] [PATCH 0 of 5 v2] Add find utility functions / exclude files from strip / reduce python Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 1 of 5 v2] Makefile.package.in: add utility functions find*clauses and notfirstword Thomas De Schampheleire
2011-11-17 19:50 ` Thomas Petazzoni
2011-11-17 20:19 ` Thomas De Schampheleire
2011-11-18 0:10 ` Arnout Vandecappelle
2011-11-18 9:41 ` Thomas De Schampheleire
2011-11-19 7:13 ` Cam Hutchison
2011-11-21 8:42 ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 2 of 5 v2] stripping: use findfileclauses utility function Thomas De Schampheleire
2011-11-18 0:06 ` Arnout Vandecappelle [this message]
2011-11-18 1:46 ` Cam Hutchison
2011-11-18 6:21 ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 3 of 5 v2] build: add option to exclude executables/dirs from being stripped Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 4 of 5 v2] python config: move configuration into menu Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 5 of 5 v2] python: allow reduced installation Thomas De Schampheleire
2011-11-17 19:55 ` Thomas Petazzoni
2011-11-18 0:24 ` Arnout Vandecappelle
2011-11-18 7:59 ` Thomas De Schampheleire
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=201111180006.04412.arnout@mind.be \
--to=arnout@mind.be \
--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