On Sunday 20 February 2011 17:31:26 Frans Meulenbroeks wrote: > 2011/2/20 Tom Rini <[email protected]>: > > On 02/20/2011 05:42 AM, Frans Meulenbroeks wrote: > >> 2011/2/19 Tom Rini<[email protected]>: > >>> On 02/19/2011 06:26 AM, Otavio Salvador wrote: > >>>> On Sat, Feb 19, 2011 at 11:52, Andreas Mueller<[email protected]> > >>>> > >>>> 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 > > Also mentioned this on irc, I will try patch 719 that is suggested > below, but this could be a toolchain issue (it would not be the > first). > Toolchain for nios is quite old (gcc 4.1.something, binutils > 2.18.50.something). It should be able to build minimal-image for distro > minimal and micro. And as far as I know neither uclibc nor eglibc are > supported. Maybe a misunderstanding on my side but: patch 719 only affects libtool-2.2 distros. I think minimal and micro distro do not pin libtool version so use libtool-2.4. > THen again it has been a while since I managed to give this attention. > > Frans. > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
