All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Doug Goldstein <cardoe@cardoe.com>, Chris Patterson <cjp256@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH 2/5] xen: drop explicit DEPEND on libgcc
Date: Tue, 26 Jan 2016 23:14:21 +0000	[thread overview]
Message-ID: <1453850061.10340.3.camel@linuxfoundation.org> (raw)
In-Reply-To: <56A78E72.6030906@cardoe.com>

On Tue, 2016-01-26 at 09:19 -0600, Doug Goldstein wrote:
> hmm. I'd rather respin it without that change then. Interesting that
> the
> NEEDED check doesn't pick it up as a dependency.

Its a known issue with the way libpthread dlopen()s libgcc. In some
ways, the pthread library should really RRECOMMEND libgcc, however
since its part of the main glibc package, that would mean libgcc
effectively everywhere.

Its only used by a limited subset of the pthread functionality so there
are cases you don't need it.

Cheers,

Richard




  reply	other threads:[~2016-01-26 23:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 15:29 [PATCH 1/5] xen: update git version to 4.6.x Doug Goldstein
2016-01-25 15:29 ` [PATCH 2/5] xen: drop explicit DEPEND on libgcc Doug Goldstein
2016-01-25 23:24   ` Chris Patterson
2016-01-26 15:19     ` Doug Goldstein
2016-01-26 23:14       ` Richard Purdie [this message]
2016-01-25 15:29 ` [PATCH 3/5] xen: fix up typo in XSM comments Doug Goldstein
2016-01-25 22:21   ` Chris Patterson
2016-01-25 15:29 ` [PATCH 4/5] xen: separate the extra steps into their own tasks Doug Goldstein
2016-01-25 22:30   ` Chris Patterson
2016-01-25 15:29 ` [PATCH 5/5] xen: move bits common to all Xen versions to xen.inc Doug Goldstein
2016-01-25 22:34   ` Chris Patterson
2016-01-25 22:20 ` [PATCH 1/5] xen: update git version to 4.6.x Chris Patterson
2016-01-26 15:58   ` Doug Goldstein

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=1453850061.10340.3.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=cardoe@cardoe.com \
    --cc=cjp256@gmail.com \
    --cc=meta-virtualization@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.