From: Colin Walters <walters@verbum.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-2.0: Fix issues with libelf dependency creeping in
Date: Mon, 07 May 2012 14:09:42 -0400 [thread overview]
Message-ID: <1336414182.2902.26.camel@lenny> (raw)
In-Reply-To: <1336384326.23777.70.camel@ted>
On Mon, 2012-05-07 at 10:52 +0100, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> diff --git a/meta/recipes-core/glib-2.0/glib-2.0/nolibelf.patch b/meta/recipes-core/glib-2.0/glib-2.0/nolibelf.patch
> new file mode 100644
> index 0000000..e9b3b26
> --- a/dev/null
> +++ b/meta/recipes-core/glib-2.0/glib-2.0/nolibelf.patch
> @@ -0,0 +1,37 @@
> +Ideally there would be configureation option for this but there is not. We
> +can't allow this code since it could detect the host system's libelf with
> +disasterous effects when cross compiling.
Random request - could you guys also CC patches to GNOME stuff to me? I
do review patches to GLib fairly actively.
As far as removing the libelf support; note this means GResource won't
work which in turn means gtk3 won't work (at the moment).
Anyways, a patch to add a configuration option is really, really trivial
if one has a checkout of git, if someone files a bug with a rationale I
can do a patch.
prev parent reply other threads:[~2012-05-07 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 9:52 [PATCH] glib-2.0: Fix issues with libelf dependency creeping in Richard Purdie
2012-05-07 16:30 ` Khem Raj
2012-05-07 18:09 ` Colin Walters [this message]
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=1336414182.2902.26.camel@lenny \
--to=walters@verbum.org \
--cc=openembedded-core@lists.openembedded.org \
/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