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
- 'micro' only builds for minimal-image and meta-toolchain, everything
else has some build problem or another.
And I'm sure I'll have more logs as I sort out my autobuilder after the
weekend.
--
Tom Rini
Mentor Graphics Corporation
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
