From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] uclibc.inc: uclibc rtld does support GNU_HASH
Date: Wed, 9 May 2012 10:55:31 -0500 [thread overview]
Message-ID: <4FAA9373.1030901@windriver.com> (raw)
In-Reply-To: <CAMKF1sp2x-JmNkx4+Exg=jFndVk_mfTfvNLO7DrUB-KhZPqbGw@mail.gmail.com>
On 5/9/12 10:47 AM, Khem Raj wrote:
> On Wed, May 9, 2012 at 7:49 AM, Mark Hatle<mark.hatle@windriver.com> wrote:
>> The per-file "advanced" dependencies, which are not yet being used by ipkg
>> or deb, include a marker for rtld support. The libc on the system needs to
>> have a provide that it supports GNU_HASH, otherwise a missing dependency
>> occurs and the system knows the package and libc has a mismatch.
>
> I would assume that this was needed when transition for sysv hash to
> gnu hash was going on. Now that GNU_HASH is default in OE for long
> time this kind of
> makes it redundant unless I am missing something w.r.t. advanced dependency
> support. What is it exactly doing ?
In the RPM case it was for people who download random binary packages from
upstream sources and attempt to install them. If the local system doesn't
support GNU_HASH then it won't work.
I thought it was still possible to build and configure a system w/ no GNU_HASH
dependencies (or even support).
I know OE itself probably doesn't have this problem, OE-Core certainly
shouldn't.. but it's external binary package cases that cause problems.
--Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-05-09 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 0:43 [PATCH 0/2] Let uclibc provide rtld(GNU_HASH) Khem Raj
2012-05-09 0:43 ` [PATCH 1/2] uclibc.inc: uclibc rtld does support GNU_HASH Khem Raj
2012-05-09 0:59 ` Marko Lindqvist
2012-05-09 1:36 ` Khem Raj
2012-05-09 1:53 ` Marko Lindqvist
2012-05-09 2:09 ` Khem Raj
2012-05-09 14:49 ` Mark Hatle
2012-05-09 15:46 ` Marko Lindqvist
2012-05-09 23:57 ` Marko Lindqvist
2012-05-09 15:47 ` Khem Raj
2012-05-09 15:55 ` Mark Hatle [this message]
2012-05-09 0:43 ` [PATCH 2/2] classes/mirrors.bbclass: Point snapshot.debian.org mirror to working location Khem Raj
2012-05-16 18:02 ` Saul Wold
2012-05-11 17:36 ` [PATCH 0/2] Let uclibc provide rtld(GNU_HASH) Saul Wold
2012-05-11 19:09 ` Khem Raj
2012-05-16 22:37 ` Scott Garman
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=4FAA9373.1030901@windriver.com \
--to=mark.hatle@windriver.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 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.