From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nitin A Kamble <nitin.a.kamble@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 00/12] gcc dso linking change, and related fixes
Date: Fri, 21 Jan 2011 00:13:43 +0000 [thread overview]
Message-ID: <1295568823.14388.28132.camel@rex> (raw)
In-Reply-To: <cover.1295304080.git.nitin.a.kamble@intel.com>
Hi Nitin,
On Mon, 2011-01-17 at 14:45 -0800, Nitin A Kamble wrote:
> This commit set, changes the dso linking to avoid automatic linking of
> shared libraries. This caused, as expected, linking of few recipes to fail.
> All these recipes are fixed by specifying the linked libraries explicitely.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: nitin/dso_linking_change
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/dso_linking_change
>
> Thanks,
> Nitin A Kamble <nitin.a.kamble@intel.com>
We've taken these into master but I'm a bit worried and we have some
breakage still. Specifically, systemtap failed with a pthread linkage
failure.
I couldn't find systemtap using pthreads anywhere that would cause the
error so I hit google. I found:
http://lists.fedoraproject.org/pipermail/devel/2010-January/129131.html
http://lists.fedoraproject.org/pipermail/devel/2010-January/129134.html
So I'm wondering if we should disable the gcc patch until Fedora sort
this out. Could you look into this and see if there are any patches
fixing this properly out there yet?
It does clearly indicate that adding -lpthread to the makefile for
systemtap would be wrong. I'm hoping that there weren't any other cases
like this?
Cheers,
Richard
next prev parent reply other threads:[~2011-01-21 0:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 22:45 [PATCH 00/12] gcc dso linking change, and related fixes Nitin A Kamble
2011-01-17 22:45 ` [PATCH 01/12] gcc_4.5.1: add DSO linking change patch Nitin A Kamble
2011-01-17 22:45 ` [PATCH 07/12] xtscal: fix build issue with gcc dso linking change Nitin A Kamble
2011-01-17 22:45 ` [PATCH 03/12] libmusicbrainz: fix the build failure caused by gcc dso linkcing change Nitin A Kamble
2011-01-17 22:45 ` [PATCH 04/12] oprofileui: fix the build failure after gcc dso change Nitin A Kamble
2011-01-17 22:45 ` [PATCH 02/12] sat-solver: fix the build failure caused by gcc dso linkcing change Nitin A Kamble
2011-01-17 22:45 ` [PATCH 06/12] matchbox-desktop: fix build issue with gcc dso linking change Nitin A Kamble
2011-01-17 22:45 ` [PATCH 05/12] settings-daemon: fix build error with new " Nitin A Kamble
2011-01-17 22:45 ` [PATCH 12/12] screenshot: fix build issue with " Nitin A Kamble
2011-01-18 3:40 ` Mark Hatle
2011-01-18 4:16 ` Kamble, Nitin A
2011-01-19 0:38 ` Kamble, Nitin A
2011-01-17 22:45 ` [PATCH 09/12] fstests: " Nitin A Kamble
2011-01-17 22:45 ` [PATCH 10/12] dates: " Nitin A Kamble
2011-01-18 3:39 ` Mark Hatle
2011-01-18 4:14 ` Kamble, Nitin A
2011-01-17 22:45 ` [PATCH 11/12] matchbox-stroke: : " Nitin A Kamble
2011-01-17 22:45 ` [PATCH 08/12] blktrace: " Nitin A Kamble
2011-01-21 0:13 ` Richard Purdie [this message]
2011-01-21 16:39 ` [PATCH 00/12] gcc dso linking change, and related fixes Kamble, Nitin A
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=1295568823.14388.28132.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=nitin.a.kamble@intel.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox