From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] glib-2.0: fix a compilation issue due to dtrace
Date: Fri, 22 Jul 2011 00:22:10 -0700 [thread overview]
Message-ID: <4E292522.801@linux.intel.com> (raw)
In-Reply-To: <eafb85c6bdc1904c6d99ae3fee97298fc5798f2b.1311246527.git.nitin.a.kamble@intel.com>
On 07/21/2011 04:09 AM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> With multilib& x32 builds dtrace is getting turned-on by the glib-2.0
> configure, which causes following compilation failure.
>
> | x86_64-linux-libtool: link: ccache gcc
> -isystem/disk0/pokybuild/build-multilib/tmp/sysroots/x86_64-linux/usr/include
> -O2 -pipe -Wall -Wl,-rpath-link
> -Wl,/disk0/pokybuild/build-multilib/tmp/sysroots/x86_64-linux/usr/lib
> -Wl,-rpath
> -Wl,/disk0/pokybuild/build-multilib/tmp/sysroots/x86_64-linux/usr/lib
> -Wl,-O1 -o .libs/gtester gtester.o
> -L/disk0/pokybuild/build-multilib/tmp/sysroots/x86_64-linux/usr/lib
> ./.libs/libglib-2.0.so -lrt -Wl,-rpath
> -Wl,/disk0/pokybuild/build-multilib/tmp/sysroots/x86_64-linux/usr/lib
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_SLICE_ALLOC'
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_REALLOC'
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_SLICE_FREE'
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_ALLOC'
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_FREE'
> | ./.libs/libglib-2.0.so: undefined reference to `GLIB_QUARK_NEW'
> | collect2: ld returned 1 exit status
> | make[4]: *** [gtester] Error 1
>
> Signed-off-by: Nitin A Kamble<nitin.a.kamble@intel.com>
> ---
> meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb | 2 +-
> meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb b/meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb
> index 0b30d17..26fc8fb 100644
> --- a/meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb
> +++ b/meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb
> @@ -1,6 +1,6 @@
> require glib.inc
>
> -PR = "r5"
> +PR = "r6"
>
Why do you bump the PR here?
Sau!
> SRC_URI = "${GNOME_MIRROR}/glib/2.27/glib-${PV}.tar.bz2 \
> file://configure-libtool.patch \
> diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb b/meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb
> index a2e609f..dce6802 100644
> --- a/meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb
> +++ b/meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb
> @@ -1,6 +1,6 @@
> require glib.inc
>
> -PR = "r2"
> +PR = "r3"
> PE = "1"
>
> SRC_URI = "${GNOME_MIRROR}/glib/2.28/glib-${PV}.tar.bz2 \
> @@ -20,3 +20,4 @@ SRC_URI[sha256sum] = "222f3055d6c413417b50901008c654865e5a311c73f0ae918b0a9978d1
>
> BBCLASSEXTEND = "native"
>
> +EXTRA_OECONF_append = " --enable-dtrace=no"
next prev parent reply other threads:[~2011-07-22 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 11:09 [PATCH 0/1] redo the glib-2.0 fix nitin.a.kamble
2011-07-21 11:09 ` [PATCH 1/1] glib-2.0: fix a compilation issue due to dtrace nitin.a.kamble
2011-07-22 7:22 ` Saul Wold [this message]
2011-07-22 15:40 ` [PATCH 0/1] redo the glib-2.0 fix Saul Wold
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=4E292522.801@linux.intel.com \
--to=sgw@linux.intel.com \
--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