Re: [PATCH] insane.bbclass: Make RPATH a non-fatal error

[Tom Rini <tom_rini@mentor.com>]

On 02/20/2011 08:05 AM, Andreas Mueller wrote:
> On Sunday 20 February 2011 15:46:48 Tom Rini wrote:
>> On 02/20/2011 05:42 AM, Frans Meulenbroeks wrote:
>>> 2011/2/19 Tom Rini<tom_rini@mentor.com>:
>>>> On 02/19/2011 06:26 AM, Otavio Salvador wrote:
>>>>> On Sat, Feb 19, 2011 at 11:52, Andreas Mueller<schnitzeltony@gmx.de>
>>>>>
>>>>>    wrote:
>>>>>> On Saturday 19 February 2011 10:45:38 Frans Meulenbroeks wrote:
>>>>>>> I am fine with the patch, but perhaps a better solution would be to
>>>>>>> introduce a var to decide whether it is a fatal or not.
>>>>>>> That way people distro's that use libtool 2.4 can decide to make it a
>>>>>>> fatal. (or individual users in their local.conf)
>>>>>>>
>>>>>>> Frans
>>>>>>
>>>>>> How comes that I sometimes feel handled as spammer ;-) ?
>>>>>>
>>>>>> see http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-
>>>>>> February/029534.html
>>>>>>
>>>>>> anyway - treating RPATH errors as fatal has lead to many QA fixes and
>>>>>> further
>>>>>> will follow...
>>>>>>
>>>>>> my opinion now: keep RPATH errors fatal as developer's  whip :-)
>>>>>
>>>>> I agree about keeping it configurable.
>>>>>
>>>>> Besides I think that we ought to keep it fatal until quite near of
>>>>> release since we'll be "forced" to fix most of many of them.
>>>>
>>>> I just want to state, again, that most of these just go away with
>>>> libtool 2.4.  Now, if people are looking for something to work on that
>>>> won't just go away with an update to libtool 2.4:
>>>> - iscsi-target needs some love again for various kernel versions as that
>>>> looks to be killing calamari and neek for nas-server-image
>>>
>>> Peeked at iscsi-target for calamari. Some inet fields have changed
>>> name in 2.6.32 or so, and apparently this is not handled fully.
>>> Instead of trying to fix it, I moved the calamari recipe to 2.6.34
>>> (which I'm already using for half a year or so, but apparently never
>>> pushed).
>>
>> Thanks.
>>
>>> I'll also see if I can update the neek version (probably also by
>>> moving the kernel version forward.
>>> Tomorrow I'll discuss this with Walter who afaik is the only other neek
>>> user.
>>
>> Note that I also see:
>> - uclibc total failure, but I assume unsupported and I'll drop
>> - minimal fails everywhere else with:
>> ERROR: QA Issue with staging: libsupc++.la failed sanity test (workdir)
>> in path
>> /var/hudson/workspace/sb_openembedded_autobuilder/BBPKGS/native-sdk-image/D
>> ISTRO/minimal/MACHINE/neek/label/sb-u1004/tmp/sysroots/nios2-linux/usr/lib
>> ERROR: QA Issue with staging: libstdc++.la failed sanity test (workdir) in
>> path
>> /var/hudson/workspace/sb_openembedded_autobuilder/BBPKGS/native-sdk-image/D
>> ISTRO/minimal/MACHINE/neek/label/sb-u1004/tmp/sysroots/nios2-linux/usr/lib
>> ERROR: QA staging was broken by the package built above
> Can you try this with the cross.bbclass patch?

I'll do a smaller subset test for that patch once the big build is done 
(I hope less than 24h left for that).

-- 
Tom Rini
Mentor Graphics Corporation