All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Haupt <andre@bitwigglers.org>
To: jani.uusi-rantala@nokia.com
Cc: yocto@yoctoproject.org
Subject: Re: glib-2.0-native build fails on bernard
Date: Fri, 12 Aug 2011 11:45:22 +0200	[thread overview]
Message-ID: <20110812094522.GA24048@localhost.localdomain> (raw)
In-Reply-To: <B497E783C723AE4386DDEA96AF1D2B989EED6E@008-AM1MPN1-013.mgdnok.nokia.com>

On Fri, Aug 12, 2011 at 08:32:17AM +0000, jani.uusi-rantala@nokia.com wrote:
> I had the same issue on 64-bit fedora R15. This patch fixed it for me:
> 
> http://patchwork.openembedded.org/patch/8233/

for bernard (with MACHINE ??= qemux86 and DISTRO ?= poky) glib-2.0_2.26.1.bb is pulled in, so the above
patch does not apply. I tried something similar:

diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.26.1.bb
b/meta/recipes-core/glib-2.0/glib-2.0_2.26.1.bb
index eace71a..e8964d9 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.26.1.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.26.1.bb
@@ -1,7 +1,7 @@
 require glib.inc
 
 PE = "1"
-PR = "r0"
+PR = "r1"
 
 SRC_URI =
"http://ftp.gnome.org/pub/GNOME/sources/glib/2.26/glib-${PV}.tar.bz2 \
            file://configure-libtool.patch \
@@ -14,3 +14,5 @@ SRC_URI[sha256sum] =
"7a74ff12b6b9dee1f2d0e520b56b68b621920c4f4250bdf23468e51562
 
 SRC_URI_append_virtclass-native = " file://glib-gettextize-dir.patch"
 BBCLASSEXTEND = "native"
+
+EXTRA_OECONF_append = " --enable-dtrace=no"

Unfortunately that does not help.

cheers,

Andre


  reply	other threads:[~2011-08-12  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12  8:26 glib-2.0-native build fails on bernard Andre Haupt
2011-08-12  8:32 ` jani.uusi-rantala
2011-08-12  9:45   ` Andre Haupt [this message]
2011-08-15  9:47     ` Andre Haupt
2011-08-15 10:05       ` Richard Purdie
2011-08-15 10:20         ` Andre Haupt

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=20110812094522.GA24048@localhost.localdomain \
    --to=andre@bitwigglers.org \
    --cc=jani.uusi-rantala@nokia.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.