On 5/9/12 10:47 AM, Khem Raj wrote:
On Wed, May 9, 2012 at 7:49 AM, Mark Hatle<mark.ha...@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
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
