All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] glibc: Upgrade to 2.25
Date: Wed, 11 Jan 2017 15:56:56 +0000	[thread overview]
Message-ID: <1484150216.3966.19.camel@pbcl.net> (raw)
In-Reply-To: <CAJTo0LZYiqp+b7hwsGaZDKbpwo4UPxyLLw7Eje1-Y5Fg-=Jwow@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

On Wed, 2017-01-11 at 12:19 +0000, Burton, Ross wrote:
> 
> > On 11 January 2017 at 03:51, Khem Raj <raj.khem@gmail.com> wrote:
> > > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> 
> > This fails when building gdk-pixbuf for x86-64 with gobject-
introspection enabled:
> 
> > > > > > > > > > > > | /data/poky-master/tmp-glibc/work/corei7-64-poky-linux/gdk-
pixbuf/2.36.1-r0/build/gdk-pixbuf/tmp-
introspectylz98kc7/.libs/GdkPixbuf-2.0: Relink `/data/poky-
master/tmp-glibc/sysroots/intel-corei7-64//usr/lib/libpng16.so.16'
with `/data/poky-master/tmp-glibc/sysroots/intel-corei7-
64//lib/libpthread.so.0' for IFUNC symbol `longjmp'
> > > The gdk-pixbuf link does use -lpthread, is this saying that libpng
should be linked against pthread too?  I can replicate on demand if
you have any suggestions.
> 
> 

That's what it's saying, and this was introduced by the fix for:

https://sourceware.org/bugzilla/show_bug.cgi?id=20019

But I think this new behaviour is in itself a bug.  It isn't reasonable
to expect any library that calls longjmp() to link -lpthread just in
case it might end up coexisting with another library that does.  (The
fact that libpthread defines longjmp is arguably a bug in itself, but
one that we are stuck with.)

p.


[-- Attachment #2: Type: text/html, Size: 1935 bytes --]

  reply	other threads:[~2017-01-11 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  3:51 [PATCH 1/2] grub-git: Upgrade to tip of master and fix with glibc 2.25 Khem Raj
2017-01-11  3:51 ` [PATCH 2/2] glibc: Upgrade to 2.25 Khem Raj
2017-01-11 12:19   ` Burton, Ross
2017-01-11 15:56     ` Phil Blundell [this message]
2017-01-11 16:21       ` Khem Raj
2017-01-11 16:54         ` Phil Blundell
2017-01-13 18:45     ` Phil Blundell
2017-01-13 18:52       ` Khem Raj
2017-01-13 20:20         ` Phil Blundell
2017-01-11 15:44   ` Phil Blundell
2017-01-11 15:53     ` Burton, Ross
2017-01-11 16:09     ` Khem Raj

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=1484150216.3966.19.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@intel.com \
    /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.