Hi Helmut, On Tue, 2018-01-02 at 09:42 +0100, Helmut Grohne wrote: > For example, it FTBFS with gcc-8 atm.
Could you please file a bug for that. I am not aware of any such issue. So would like to fix it, and would if I knew about it. Thanks. > Even if that checking was happening in > practise, the release pace of elfutils is much too low to catch up > with compilers. You are always going to loose on this whac-a-mole. > Practically you are outsourcing that checking of new compilers to > downstream users. When reported in the past, such issues were not > fixed in a timely manner. My apologies for not fixing such issues in the past fast enough. We try to push out a release every 3 to 4 months. And in general we do try to fix any bugs and make patches available upstream as quickly as possible. For example Fedora often does trial runs with newer compilers and if they report an issue we try to get a fix asap. But we can only fix them if they get reported. > Making builds fail on warnings hides fatal errors > would that occur later. It makes us blind to the real problems and > since it delays the finding of problems, it also makes them harder > and more costly to track down. My experience is the opposite. With make distcheck we even make sure the build is valgrind and gcc -fsanitize-undefined clean. Which has caught many issues early. > A method that is way more effective at finding the problems you are > after is setting up some CI service to use a variety of compilers > with -Werror. We do currently have a buildbot for elfutils, but it isn't widely publized yet. Currently we do not have a gcc-8 setup, but that could be added: https://builder.wildebeest.org/buildbot/#/builders?tags=elfutils It currently does centos, debian, fedora on x86_64, amd64, i386, ppc64, ppc64le and s390x. If you could provide other workers that would be appreciated. Thanks, Mark
