On 4/25/13 3:43 PM, Ian Geiser wrote:
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Martin Jansa
Sent: Wednesday, April 24, 2013 3:20 AM
To: [email protected]
Subject: [OE-core] debugedit: canonicalization unexpectedly shrank by
one character
Hi,
with debugedit errors now catched and shown after:
commit 262a69ffd33e9d001a7a15fc73671a015e3b5dd1
Author: Richard Purdie <[email protected]>
Date: Mon Mar 25 16:52:07 2013 +0000
package.bbclass: Handle subprocess errors correctly
If an error occurs in subprocess.call() we currently don't catch
it. In particular
we have issues where debugedit is segfaulting unnoticed. This fixes
up
various code paths to catch the errors.
I get couple of recipes failing with errors like:
[...]
This leads to
https://bugzilla.redhat.com/show_bug.cgi?id=304121
https://bugs.launchpad.net/rpm/+bug/638633
https://qa.mandriva.com/show_bug.cgi?id=62391
but no clear solution (it would be nice to show which path triggered
that message as suggested in redhat bugzilla)
I can INHIBIT_PACKAGE_DEBUG_SPLIT in failing recipes or adding slash to
-d '/usr/src/debug/' works in this case too..
I tried set PACKAGE_DEBUG_SPLIT_STYLE = "debug-without-src" in the package and
that seemed to work around the problem. In my package that was offending was because
there was an -rpath that had a trailing /. It seems debugedit is very sensitive to rogue
path separators. Are there ways to make this more robust?
Source for debugedit is part of RPM. I don't see any reason why we wouldn't
accept patches for something like this. (However, it does seem like the rpath
may be wrong as well. Fixing the rpath should probably be done as well.)
--Mark
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
