Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] elfutils: Add a --{enable, disable}-backends option
Date: Wed, 1 Apr 2015 21:43:23 +0200	[thread overview]
Message-ID: <20150401214323.4e340217@free-electrons.com> (raw)
In-Reply-To: <1427911925-7424-1-git-send-email-heyleke@gmail.com>

Dear Jan Heylen,

On Wed,  1 Apr 2015 20:12:05 +0200, Jan Heylen wrote:

> diff --git a/package/elfutils/0007-backends-configurable.patch b/package/elfutils/0007-backends-configurable.patch
> new file mode 100644
> index 0000000..b93e2da
> --- /dev/null
> +++ b/package/elfutils/0007-backends-configurable.patch

Patches should have a description and a Signed-off-by line.

Also, could you submit this patch upstream? I'd like to see if upstream
is willing to accept such a patch, since it is more or less a "feature"
patch, and we prefer to not have to carry such patches forever.

> +config BR2_PACKAGE_ELFUTILS_BACKENDS
> +	bool "Build and install backend shared libraries"
> +	default y
> +	help
> +	  This option tells elfutils to not only install the libelf
> +	  libraries, but also the libebl backend shared libraries
> +	  with architecture specific code to read elf files. If you
> +	  intend to use libelf/libebl at-runtime, say 'y' here.
> +	  If you only need to link against libelf at-compile-time,
> +	  but not really using it, you can leave the architecture
> +	  specific backends uninstalled. Loading of the backend library
> +	  by libebl will fail in that case.

This explanation seems weird: why would you link against libelf and not
use it?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-01 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 18:12 [Buildroot] [PATCH 1/1] elfutils: Add a --{enable, disable}-backends option Jan Heylen
2015-04-01 19:43 ` Thomas Petazzoni [this message]
2015-04-02  7:12   ` Jan Heylen
2015-04-02  7:23     ` Thomas Petazzoni
2015-04-02  7:26       ` Jan Heylen

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=20150401214323.4e340217@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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