Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11416] check-uniq-files staging issue
Date: Mon, 22 Oct 2018 07:33:41 +0000	[thread overview]
Message-ID: <bug-11416-163-vYSBbaxHKg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11416-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11416

--- Comment #1 from Jean-pierre Cartal <jpcartal@free.fr> ---
The following patch avoids the false positive warnings regarding .la files: 
diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
index a689dde4d2..110f8ee4a5 100644
--- a/package/pkg-generic.mk
+++ b/package/pkg-generic.mk
@@ -276,7 +276,8 @@ $(BUILD_DIR)/%/.stamp_staging_installed:
                                $(addprefix
$(STAGING_DIR)/usr/bin/,$($(PKG)_CONFIG_SCRIPTS)) ;\
        fi
        @$(call MESSAGE,"Fixing libtool files")
-       $(Q)find $(STAGING_DIR)/usr/lib* -name "*.la" | xargs --no-run-if-empty
\
+       $(Q)for lafile in $$(find $(@D) -name *.la -exec basename {} \; | sort
-u); do \
+               ls $(STAGING_DIR)/usr/lib*/$${lafile}; done | xargs
--no-run-if-empty \
                $(SED) "s:$(BASE_DIR):@BASE_DIR@:g" \
                        -e "s:$(STAGING_DIR):@STAGING_DIR@:g" \
                        $(if $(TOOLCHAIN_EXTERNAL_INSTALL_DIR),\

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2018-10-22  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22  7:22 [Buildroot] [Bug 11416] New: check-uniq-files staging issue bugzilla at busybox.net
2018-10-22  7:33 ` bugzilla at busybox.net [this message]
2019-02-15 22:06 ` [Buildroot] [Bug 11416] " bugzilla at busybox.net
2019-11-29 13:08 ` 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-11416-163-vYSBbaxHKg@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