iproute2: only link libelf where needed
authorJo-Philipp Wich <jo@mein.io>
Wed, 19 Dec 2018 08:50:05 +0000 (09:50 +0100)
committerJo-Philipp Wich <jo@mein.io>
Wed, 19 Dec 2018 09:50:02 +0000 (10:50 +0100)
commit386803a006edafd54cef20b4b99b033b1b52cf5c
tree386a347b0c00041430c64184b712d24ea62a559e
parent4b4e6a04ac918d5cce2d168d9e656f3d2a29ec4b
iproute2: only link libelf where needed

The iproute2 build system links libelf support to every utility while only
the tc program actually requires libelf specific functionality.

Unfortunately the BPF ELF functionality is not confined into an own
compilation unit but added to the existing bpf.c sources of the shared
static libutil.a, causing every iproute2 applet to pick up an implicit
libelf.so dependency.

In order to avoid this requirement, patch the iproute2 build system to
create both a libutil.a and a libutil-elf.a, with the former being built
without libelf functionality and to only link the tc applet with the libelf
enabled libutil.

Finally, make the tc package depend on libelf to solve compilation errors.

Ref: https://github.com/openwrt/packages/issues/7728
Fixes: FS#2011
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
package/network/utils/iproute2/Makefile
package/network/utils/iproute2/patches/190-link-libelf-to-tc-only.patch [new file with mode: 0644]