[pkg-bacula-devel] Silencing the build log scanner

Sven Hartge sven at svenhartge.de
Wed Nov 14 01:55:55 GMT 2018

On 13.11.18 21:37, Carsten Leonhardt wrote:

> Hmm, I mainly see blhc complaining about the bat compilation
About that part: I tried several iterations of manually setting CFLAGS
and CPPFLAGS (which cmake does not honor), adding those changes to the
hardening patch to add the flags to QMAKE_CFLAGS and QMAKE_CPPFLAGS but
nothing stuck. I am totally at loss, where the flags present come from
and why it is seemingly not possible to override them.

I dislike qmake and cmake more and more, after each time encountering
them. (And don't get me started on the odyssey I had to do to add
"strace" to the qt5-rcc call to debug the CI failure.)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20181114/108161f2/attachment.sig>

More information about the pkg-bacula-devel mailing list