All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] insane.bbclass: Make RPATH a non-fatal error
Date: Sun, 20 Feb 2011 07:46:48 -0700	[thread overview]
Message-ID: <4D612958.70402@mentor.com> (raw)
In-Reply-To: <AANLkTim-b=vO2vD5sgTo5bKduF=OYqAczS7f3YYdgPUy@mail.gmail.com>

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/DISTRO/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/DISTRO/minimal/MACHINE/neek/label/sb-u1004/tmp/sysroots/nios2-linux/usr/lib
ERROR: QA staging was broken by the package built above

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-02-20 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 19:26 [PATCH] insane.bbclass: Make RPATH a non-fatal error Tom Rini
2011-02-18 19:33 ` Khem Raj
2011-02-18 19:36 ` Tom Rini
2011-02-18 19:53   ` Denys Dmytriyenko
2011-02-18 19:54 ` Eric Bénard
2011-02-18 20:36 ` Eric Benard
2011-02-19  9:45   ` Frans Meulenbroeks
2011-02-19 11:52     ` Andreas Mueller
2011-02-19 13:26       ` Otavio Salvador
2011-02-19 16:59         ` Tom Rini
2011-02-20 12:42           ` Frans Meulenbroeks
2011-02-20 14:46             ` Tom Rini [this message]
2011-02-20 14:59               ` Eric Benard
2011-02-20 15:05               ` Andreas Mueller
2011-02-20 15:37                 ` Tom Rini
2011-02-20 16:31               ` Frans Meulenbroeks
2011-02-20 16:54                 ` Andreas Mueller
2011-02-20 17:56                   ` Frans Meulenbroeks
2011-02-20 18:26               ` Frans Meulenbroeks
2011-02-20 18:58                 ` Andreas Mueller
2011-02-19 17:33 ` Holger Freyther
2011-02-19 18:27   ` Frans Meulenbroeks
2011-02-20  1:19   ` Tom Rini

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=4D612958.70402@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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.