From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gdb: prevent installation of libbfd.so and libopcode.so
Date: Fri, 8 Dec 2017 22:29:52 +0100 [thread overview]
Message-ID: <20171208212952.20366-1-ps.report@gmx.net> (raw)
The gdb install target installs dynamic versions of libbfd and
libopcode, accidentally overwriting the binutils provided versions
(gdb itself links against the bundled static ones to avoid
version problems, so the dynamic ones are un-needed).
Prevent the installation by using the '--disable-install-libbfd'
configure option.
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
Changes v1 -> v2:
- enhance commit log (suggested by Thomas Petazzoni)
- use --disable-install-libbfd instead of --disable-shared
---
package/gdb/gdb.mk | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/gdb/gdb.mk b/package/gdb/gdb.mk
index 7e86ba0c7e..0f3846687e 100644
--- a/package/gdb/gdb.mk
+++ b/package/gdb/gdb.mk
@@ -55,9 +55,11 @@ endif
# When gdb sources are fetched from the binutils-gdb repository, they
# also contain the binutils sources, but binutils shouldn't be built,
-# so we disable it.
+# so we disable it (additional the option --disable-install-libbfd
+# prevents the un-wanted installation of libobcodes.so and libbfd.so).
GDB_DISABLE_BINUTILS_CONF_OPTS = \
--disable-binutils \
+ --disable-install-libbfd \
--disable-ld \
--disable-gas
--
2.15.0
next reply other threads:[~2017-12-08 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 21:29 Peter Seiderer [this message]
2017-12-17 9:19 ` [Buildroot] [PATCH v2] gdb: prevent installation of libbfd.so and libopcode.so Thomas Petazzoni
2017-12-27 16:35 ` Peter Korsgaard
2017-12-30 23:06 ` 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=20171208212952.20366-1-ps.report@gmx.net \
--to=ps.report@gmx.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