Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] iproute2 binaries getting linked against libelf, which is not available in target
Date: Thu, 18 Jun 2020 22:14:51 +0300	[thread overview]
Message-ID: <87o8pgkwyc.fsf@tarshish> (raw)
In-Reply-To: <021201d64596$e75979a0$b60c6ce0$@ipcomm.de>

Hi Andreas,

On Thu, Jun 18 2020, Andreas Hilse wrote:
> 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.

Section 6.1.2 in the Buildroot manual says this:

  We do not support toolchains or SDK generated by OpenEmbedded or
  Yocto, because these toolchains are not pure toolchains (i.e. just
  the compiler, binutils, the C and C++ libraries).

  https://buildroot.org/downloads/manual/manual.html#_cross_compilation_toolchain

Buildroot Can't support an external toolchain that provides its own
build of libelf, or any other library besides what gcc and the C library
provide.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  parent reply	other threads:[~2020-06-18 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 17:35 [Buildroot] iproute2 binaries getting linked against libelf, which is not available in target Andreas Hilse
2020-06-18 19:10 ` Thomas Petazzoni
2020-06-18 19:14 ` Baruch Siach [this message]
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=87o8pgkwyc.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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