Hello Simon, On 7/2/22 12:41 AM, Simon Ruderich wrote:
to quote the man-page:Ignore lines matching the given Perl regex. regex is automatically anchored at the beginning and end of the line to prevent false negatives. NOTE: Not the input lines are checked, but the lines which are displayed in warnings (which have line continuation resolved).Something like --ignore-line '/usr/bin/cc.*\S+\.S' should work.
Yes, that worked well. Thanks for the hint about the anchoring; I did read the man page, but it seems I missed that part.
There is a new problem, however. I was testing --ignore-line so I could eventually put the resulting regex in debian/rules as per this part of the man page:
To suppress false positives you can embed the following string in the build log: blhc: ignore-line-regexp: REGEXP All lines fully matching REGEXP (see --ignore-line for details) will be ignored. Please use this feature sparingly so that missing flags are not overlooked. If you find false positives which affect more packages please report a bug. To generate this string simply use echo in "debian/rules"; make sure to use @ to suppress the echo command itself as it could also trigger a false positive. If the build process takes a long time edit the ".build" file in place and tweak the ignore string until blhc --all --debian package.build no longer reports any false positives.
I added this line to debian/rules: @echo "blhc: ignore-line-regexp: '/usr/bin/cc.*\S+\.S'"and also confirmed that it was echoed in the build log, but blhc is still triggered by those lines even though the regex is identical to one that worked with --ignore-line. What am I doing wrong this time?
Thanks, -- Ben Westover
OpenPGP_signature
Description: OpenPGP digital signature
