On Mon, Sep 28, 2015 at 03:31:33PM +0200, Guillem Jover wrote: > In addition this only covers part of the problem, and might give a > false sense of knowlegde for people reading the build logs, which > might be even more confusing. Consider that any usage of > --export=cmdline or --export=configure will be missed, like the > ones in dpkg itself or pcre3.
Hello, Hm. I didn't think of --export=cmdline/configure. That's problematic. >> If you know a better solution for this issue, please implement >> it. It feels a bit hacky. > > While this is a clever solution, it indeed feels a bit too dirty. Do you have a suggestion how to implement this in a better way? I tried to add it to debhelper (#800012), but that isn't perfect either (though it should work reliably). Asking every maintainer to manually call dpkg-buildflags won't scale and checking the build log with blhc has been a good way to detect missing compiler flags in a lot of packages and I'd like to avoid false positives - but for that blhc needs to know the compiler flags after the build. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
