From mboxrd@z Thu Jan  1 00:00:00 1970
From: Baruch Siach <baruch@tkos.co.il>
Date: Thu, 18 Jun 2020 22:14:51 +0300
Subject: [Buildroot] iproute2 binaries getting linked against libelf,
 which is not available in target
In-Reply-To: <021201d64596$e75979a0$b60c6ce0$@ipcomm.de>
References: <021201d64596$e75979a0$b60c6ce0$@ipcomm.de>
Message-ID: <87o8pgkwyc.fsf@tarshish>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

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 -