On 31 July 2012 17:33, Stefan Weil <s...@weilnetz.de> wrote: > please apply http://patchwork.ozlabs.org/patch/171067/, > or we'll get a 4th bug fix for this. > > Peter sent a series with this one and more patches on > 2012-07-18 (1st: http://patchwork.ozlabs.org/patch/171686/). > At least the first 10 of them should be applied.
More accurately: * apply the valgrind patch first: http://patchwork.ozlabs.org/patch/174029/ * then apply the 11 patch configure series I believe the valgrind test patch should fix the issues Blue Swirl was seeing with the 11-patch series (and I tested it on debian squeeze which I think has the same gcc Blue was using). Patch 11/11 does enable -Werror on test code in a way which causes configure to fail noisily if it encounters a warning: I think it's better to commit this early rather than late because then we can fix any lingering problems with odd hosts or configurations which I missed. (The noisy failure includes a clear message about how to work around it in the interim, which is better than our current situation IMHO.) thanks -- PMM
