Hi,
On Fri, Apr 3, 2015 at 1:20 PM, Mark Wielaard <mjw(a)redhat.com> wrote:
Hi,
On Fri, 2015-04-03 at 10:03 +0200, Jan Heylen wrote:
> Add a --{enable,disable}-backends configuration option to elfutils. This
> allows to selectively disable the compilation of the libebl backends
> shared libraries. This is usefull when some application require linking
> against the elfutils libelf, but don't require the backends to be available
> at runtime on target, e.g. in a cross compilation setting.
I don't really like this solution since that means we are building known
broken binaries and libraries. If the backends aren't available various
things will just break or (worse) silently produce wrong results.
Could you explain what goes wrong in a cross compilation setting when
you build the backends? We might be able to fix this differently.
(Please assume I don't know how to actually setup a cross compilation
setting, I never cross compiled elfutils, but I am happy to learn.)
The problem in cross compilation setup is the consumed space (even
when stripped), in my setup (created with buildroot), I don't need the
backends, so I want to tell elfutils package not to compile them and
not to install them
(see:
http://lists.busybox.net/pipermail/buildroot/2015-April/123978.html)
Jan
Thanks,
Mark