Re: Recent OBJDUMP changes

[Marcin Juszkiewicz <openembedded@hrw.one.pl>]

Dnia poniedziałek, 4 grudnia 2006 21:34, Leon Woestenberg napisał:

> My assumption was wrong, the correct (cross-toolchain) objdump is used.
>
> However, the shlibs system seems to fail elsewhere, this is what I see
> if I disable the objdump command error redirection "2>/dev/null" in
> package.bbclass:

> NOTE: Couldn't find shared library provider for libc.so.6

Does someone found better fix then mine?

[hrw@misc1 classes]$ mtn dif package.bbclass
#
# old_revision [76f1fdf6dff425bfdddcd67c4430bf4bc23ab36c]
#
# patch "classes/package.bbclass"
#  from [b4538ccc18abcaa057513563f37b2d25fdce5784]
#    to [969285b9af2e3bc59048d34cf396dd529e496c1e]
#
============================================================
--- classes/package.bbclass     b4538ccc18abcaa057513563f37b2d25fdce5784
+++ classes/package.bbclass     969285b9af2e3bc59048d34cf396dd529e496c1e
@@ -576,6 +576,7 @@ python package_do_shlibs() {
                                path = os.path.join(root, file)
                                if os.access(path, os.X_OK) or lib_re.match(file):
                                        cmd = bb.data.getVar('OBJDUMP', d, 1) + " -p " + path + " 2>/dev/null"
+                                       cmd = "PATH=\"%s\" %s" % (bb.data.getVar('PATH', d, 1), cmd)
                                        fd = os.popen(cmd)
                                        lines = fd.readlines()
                                        fd.close()
[hrw@misc1 classes]$

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

      I don't know. I don't care. And it doesn't make any difference.