From: Andreas Hilse <andreas.hilse@ipcomm.de>
To: buildroot@busybox.net
Subject: [Buildroot] iproute2 binaries getting linked against libelf, which is not available in target
Date: Thu, 18 Jun 2020 19:35:48 +0200 (CEST) [thread overview]
Message-ID: <021201d64596$e75979a0$b60c6ce0$@ipcomm.de> (raw)
Hi,
I found an issue with buildroot 2020.02.x concerning iproute2 binaries
being linked against libelf.
According to iproute2.mk it should only link against libelf if
BR2_PACKAGE_ELFUTILS is selected.
But it also links against libelf without that option selected and thus
renders the created binaries unusable in the target system.
After digging further I found that this is due to the iproute2 configure
script detecting libelf being available in the used toolchain
(crosstool-ng companion library).
After finding out I can work around this issue.
I thought this might be a thing to be addressed in buildroot, but I'm not
sure how to approach it.
Best regards
Andreas Hilse
next reply other threads:[~2020-06-18 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 17:35 Andreas Hilse [this message]
2020-06-18 19:10 ` [Buildroot] iproute2 binaries getting linked against libelf, which is not available in target Thomas Petazzoni
2020-06-18 19:14 ` Baruch Siach
2020-06-19 6:31 ` Andreas Hilse
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='021201d64596$e75979a0$b60c6ce0$@ipcomm.de' \
--to=andreas.hilse@ipcomm.de \
--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