as discussed on irc, it'd be nice to have a mechanism to filter stderr to catch warnings and such and abort the build specifically, we'd like to catch 'dereferencing type-punned pointer will break strict-aliasing rules' warnings since these almost always end up with runtime bugs/crashes
...and as discussed on irc, come up with a filter, and I can do the modification to handle it. Nee stderr only, or?
*** This bug has been marked as a duplicate of 155597 ***
Opp, I meant to dupe it the other way.
*** Bug 155597 has been marked as a duplicate of this bug. ***
thinking about this, we already have most parts in place ... if the user has PORTAGE_LOGDIR set, then we have a full build log we can work with, so really the case is where the user hasnt set that variable what i propose is: - set PORTAGE_LOGFILE in environment that points to the relevant build output - if user does not have PORTAGE_LOGDIR set, then pretend they have it set to $T - in install_qa_check(), we can add grep's and what not to work on the logfile should be trivial to do this now
ok, i've merged my previous idea with help from zmedico ... i've also integrated the aforementioned pointer scanner code this stuff only spits out QA Notices in the normal scenario ... if you have FEATURES=stricter, then it'll abort ... we'll see how well that flies and how we need to tweak this behavior and/or the messages scanned for
thanks!
What we've got now has been released in 2.1.2_rc4-r6.
2.1.2 final has been released.
