Hi, Executive summary: the build failures are mostly solved -- save for one test failure on m68k.
On Thursday, December 1, 2016 1:16:43 PM CST David Kalnischkies wrote: > So @googletest maintainers, please state what you can/want to do about > it or not. Being a build-dependency of apt provides some benefits, ... such as ? :-) > also carries a cost in that there basically is no distinction between > release, non-release and unofficial port architectures. If you > can't/won't pay that price that is fine, we (as in deity@l.d.o) just > need to know and we will figure something out – I just want to ask first > before we rush into evaluating and moving to other testing frameworks, > which is time better spent on other bugs if we can help it… OK, so the root cause of the issues was that one of the tests in googletest's own test suite was failing when I first built it. The failure went away if I built without optimization, so that is what I did for the first 3 uploads (the build is ONLY used for the test suite, so I figured lack of optimization is acceptable). I don't know whether this failure (gtest_catch_exceptions_test) is a bug in GoogleTest or in Debian's toolchain as no-one else seems to be reporting it. Anyway, for some reason, building with no optimization caused failures in many architectures -- typically overflowing a symbol table; c.f. #845274. It was surprising to me that optimiziation would affect the number of symbols produced. In any case, rev 3 fixed that issue but inadvertently caused a different set of problems because setting CXXFLAGS disables the dpkg hardening flags. Rev 4 fixes that, re-enables optimization, but drops the failing test. There are two architectures left to hear from, but -- apart from m68k -- all others have successfully built now. I do intend to look into the m68k failure, but would really appreciate some help with it. And with the failure of gtest_catch_exceptions_test -- which I'd prefer to reinstate once fixed. I'm not certain what the original question was, but maybe the above helps. If not, please elaborate. Best, -Steve
signature.asc
Description: This is a digitally signed message part.
