);
my %buildd_tag = (
- no_compiler_commands => 'W-no-compiler-commands',
+ no_compiler_commands => 'I-no-compiler-commands',
non_verbose_build => 'W-compiler-flags-hidden',
flags_missing => 'W-dpkg-buildflags-missing',
hardening_wrapper => 'I-hardening-wrapper-used',
- invalid_cmake => 'W-invalid-cmake-used',
+ invalid_cmake => 'I-invalid-cmake-used',
);
# Statistics of missing flags and non-verbose build commands. Used for
=over 2
-=item
+=item *
Print tags instead of normal warnings, see L</"BUILDD TAGS"> for a list of
possible tags.
-=item
+=item *
Don't check hardening flags in old log files (if dpkg-dev << 1.16.1 is
detected).
-=item
+=item *
Don't require Term::ANSIColor.
=over 2
-=item
-
-B<I-hardening-wrapper-used>
+=item B<I-hardening-wrapper-used>
The package uses hardening-wrapper which intercepts calls to gcc and adds
hardening flags. The build log doesn't contain any hardening flags and thus
can't be checked by blhc.
-=item
-
-B<W-compiler-flags-hidden> (summary of hidden lines)
+=item B<W-compiler-flags-hidden> (summary of hidden lines)
Build log contains lines which hide the real compiler flags. For example:
in a F<Makefile> must be removed. And as last resort the F<Makefile> must be
patched to remove the C<@>s hiding the real compiler commands.
-=item
-
-B<W-dpkg-buildflags-missing> (summary of missing flags)
+=item B<W-dpkg-buildflags-missing> (summary of missing flags)
CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS missing.
-=item
-
-B<W-invalid-cmake-used> (version)
-
-=item
+=item B<I-invalid-cmake-used> (version)
-B<W-no-compiler-commands>
+=item B<I-no-compiler-commands>
No compiler commands were detected. Either the log contains none or they were
not correctly detected by blhc (please report the bug in this case).