From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-autotools: explicitly use /usr/{bin, sbin, lib}, with merged usr
Date: Wed, 1 Nov 2017 01:36:27 -0200 [thread overview]
Message-ID: <20171101033627.26253-1-casantos@datacom.ind.br> (raw)
Prevent packages from using /bin, /sbin or /lib when those paths are
symlinks to their /usr counterparts.
This is useful for util-linux, whose installation attempts to move
shared libraries from ${usrlib_execdir} to ${libdir} if both paths are
not the same, leading to error messages like this:
mv: '$(TARGET_DIR)/usr/lib/libfoo.so.1' and '$(TARGET_DIR)/lib/libfoo.so.1' are the same file
Fortunalely that error is not fatal but other packages may do similar
things with bad results, so let's avoid possible problems.
Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
---
package/pkg-autotools.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/pkg-autotools.mk b/package/pkg-autotools.mk
index 45de99356f..32e76b54c2 100644
--- a/package/pkg-autotools.mk
+++ b/package/pkg-autotools.mk
@@ -189,6 +189,7 @@ define $(2)_CONFIGURE_CMDS
--build=$$(GNU_HOST_NAME) \
--prefix=/usr \
--exec-prefix=/usr \
+ $$(if $$(BR2_ROOTFS_MERGED_USR),--bindir=/usr/bin --sbindir=/usr/sbin --libdir=/usr/lib,) \
--sysconfdir=/etc \
--localstatedir=/var \
--program-prefix="" \
--
2.13.6
next reply other threads:[~2017-11-01 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 3:36 Carlos Santos [this message]
2017-11-05 12:52 ` [Buildroot] [PATCH] pkg-autotools: explicitly use /usr/{bin, sbin, lib}, with merged usr Arnout Vandecappelle
2017-11-05 13:25 ` Thomas Petazzoni
2017-11-08 23:42 ` [Buildroot] [PATCH] util-linux: " Carlos Santos
2017-11-09 0:05 ` Carlos Santos
2017-11-22 21:46 ` Thomas Petazzoni
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=20171101033627.26253-1-casantos@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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