I am experiencing the same problem with the PyInstaller package, and have a bit of additional information to add that might be helpful.
With waf in --verbose mode, each build produces two lines, the first one listing just the name of the file to be compiled and the second listing all of the arguments. [ 1/21] Compiling src/pyi_utils.c 00:07:52 runner ['/usr/lib/ccache/gcc', '-g', '-O2', '-Werror=implicit- function-declaration', '-ffile-prefix-map=/builds/python-team/packages/ pyinstaller/debian/output/source_dir=.', '-fstack-protector-strong', '-fstack- clash-protection', '-Wformat', '-Werror=format-security', '-fcf-protection', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-m64', '-O2', '-Wall', '-Werror', '- Wno-error=unused-variable', '-Wno-error=unused-function', '-Wno-error=unused- but-set-variable', '-U_FORTIFY_SOURCE', '-Isrc', '-I../../src', '-Iwindows', '-I../../windows', '-Izlib', '-I../../zlib', '-D_REENTRANT', '-D_BSD_SOURCE', '-D_DEFAULT_SOURCE', '-D_FORTIFY_SOURCE=2', '-DHAVE_STDBOOL_H=1', '- DHAVE_UNSETENV=1', '-DHAVE_MKDTEMP=1', '-DHAVE_DIRNAME=1', '- DHAVE_BASENAME=1', '-DLAUNCH_DEBUG', '-DNDEBUG', '../../src/pyi_utils.c', '- c', '-o/builds/python-team/packages/pyinstaller/debian/output/source_dir/ bootloader/build/debug/src/pyi_utils.c.1.o', '-Wdate-time', ‘- D_FORTIFY_SOURCE=2’] https://salsa.debian.org/python-team/packages/pyinstaller/-/jobs/6712631/ viewer#L3682 Blhc doesn’t complain about the second line, but it flags the first line as being a NONVERBOSE build. 169:NONVERBOSE BUILD: [ 1/21] Compiling src/pyi_utils.c https://salsa.debian.org/python-team/packages/pyinstaller/-/jobs/6712640#L22 That either means that blhc can’t parse the second line and doesn’t recognize it as a list of compile flags, or it means it can parse the second line and approves of it. Assuming the second is the case, would it be possible to modify blhc so that, when it encounters the first line with just “Compiling” and the name of the file, it checks to see if there is a second line that also contains the name of the same file (closer to the end in this case) and also contains all the build flags? -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
