Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] Makefile: do not try to strip inexisting file when stripping libpthread
Date: Wed, 21 Aug 2013 21:33:44 +0200	[thread overview]
Message-ID: <52151618.7070900@mind.be> (raw)
In-Reply-To: <1376996584-4462-5-git-send-email-thomas.petazzoni@free-electrons.com>

On 20/08/13 13:03, Thomas Petazzoni wrote:
> libpthread.so has a special stripping condition to preserve parts of
> it that are needed for debugging. However, due to the usage of 'xargs'
> instead of 'xargs -r', the strip command is executed regardless of
> whether a libpthread.so file is found or not. This leads to a big
> error message being displayed in static-only builds, because strip is
> executed without a file argument. Thanks to the '|| true', the build
> continues, but still shows a big error message in the middle, which is
> not nice.
>
> By using 'xargs -r', we avoid the strip command from being executed
> when 'find' doesn't find any match. We also remove the '|| true' to
> catch other real errors.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

  I'd find it more natural to use the -exec option of find, but this 
patch solves a real problem so

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

> ---
>   Makefile | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 5d40126..9201f27 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -485,7 +485,7 @@ endif
>   # I set a breakpoint"
>   ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
>   	find $(TARGET_DIR)/lib -type f -name 'libpthread*.so*' | \
> -		xargs $(STRIPCMD) $(STRIP_STRIP_DEBUG) || true
> +		xargs -r $(STRIPCMD) $(STRIP_STRIP_DEBUG)
>   endif
>
>   	mkdir -p $(TARGET_DIR)/etc
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-08-21 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 11:02 [Buildroot] [PATCH 0/5] Set of fixes, for 2013.08 Thomas Petazzoni
2013-08-20 11:03 ` [Buildroot] [PATCH 1/5] attr: add patch to fix static installation Thomas Petazzoni
2013-08-23 13:28   ` Gustavo Zacarias
2013-08-20 11:03 ` [Buildroot] [PATCH 2/5] acl: " Thomas Petazzoni
2013-08-23 13:28   ` Gustavo Zacarias
2013-08-20 11:03 ` [Buildroot] [PATCH 3/5] Makefile: test before search for kernel modules Thomas Petazzoni
2013-08-21  7:08   ` Luca Ceresoli
2013-08-20 11:03 ` [Buildroot] [PATCH 4/5] Makefile: do not try to strip inexisting file when stripping libpthread Thomas Petazzoni
2013-08-21 19:33   ` Arnout Vandecappelle [this message]
2013-09-02 21:13   ` Peter Korsgaard
2013-08-20 11:03 ` [Buildroot] [PATCH 5/5] kmod: does not support static builds Thomas Petazzoni
     [not found]   ` <52151C54.9010606@mind.be>
2013-08-27 16:48     ` Thomas Petazzoni
2013-09-02 21:32   ` Peter Korsgaard

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=52151618.7070900@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