All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libgcc not being pulled into OABI images
Date: Mon, 31 Mar 2008 01:40:10 +0200	[thread overview]
Message-ID: <47F024DA.5020502@gmx.de> (raw)
In-Reply-To: <1206911981.4838.12.camel@dax.rpnet.com>

Hi,

I tested on my host machine (AMD64) and libgcc is not it NEEDED but is 
installed anyway. So it seems to be no problem that libgcc is not in 
needed. So I investigated libpthread and found out that it tries to 
dlopen libgcc and fails if it can't. Our shlibs code can't detect this 
so libgcc does not get pulled into image. So I suggest something like:

--- packages/glibc/glibc.inc    e9a2a880277298ca08e7f53a4e5c69127415a5ed
+++ packages/glibc/glibc.inc    3aa1e1a80cf9f0f899b5a79b857bfa5427f5d54e
@@ -7,6 +7,8 @@ DEPENDS = "${@['virtual/${TARGET_PREFIX}
 DEPENDS = "${@['virtual/${TARGET_PREFIX}gcc-initial', 
'virtual/${TARGET_PREFIX}gcc']['nptl' in '${GLIBC_ADDONS}']} 
linux-libc-headers"
 #this leads to circular deps, so lets not add it yet
 #RDEPENDS_ldd += " bash"
+# nptl needs libgcc but dlopens it, so our shlibs code doesn't detect this
+RDEPENDS += "${@['','libgcc']['ntpl' in '${GLIBC_ADDONS}']}"
 PROVIDES = "virtual/libc ${@['virtual/${TARGET_PREFIX}libc-for-gcc', 
'']['nptl' in '${GLIBC_ADDONS}']}"
 PROVIDES += "virtual/libintl virtual/libiconv"


Is it ok if I comit this (and bump PRs of all packages that use this file?)

Regards,
Thomas



  reply	other threads:[~2008-03-30 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 21:19 libgcc not being pulled into OABI images Richard Purdie
2008-03-30 23:40 ` Thomas Kunze [this message]
2008-04-02  6:17   ` Khem Raj
2008-04-03 12:26   ` Rolf Leggewie

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=47F024DA.5020502@gmx.de \
    --to=thommycheck@gmx.de \
    --cc=openembedded-devel@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 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.