Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
command not found QA: don't skip QA warnings that come from ./configure
Down through the twisting trail of history, we find a 2008 bug report and commit 930bbbf, which disabled detecting "command not found" in ./configure scripts with the following rationale: > This is actually a false positive. I'll fix it to filter out the ones that are generated by configure scripts. As far as I can tell it wasn't a false positive though. Looking up the source code for that old project reveals no indication that it can misfire in "expected" ways. More generally, this obscures real issues in configure scripts -- why should configure scripts be special here? -- which have *zero* guarantee of resulting in failure. Anecdotally, they usually do not. Whatever the underlying issue is, it's *definitely* an upstream bug and *almost certainly* indicates that there may be situations where the project miscompiles against expectations. Bug: https://bugs.gentoo.org/245716 Signed-off-by: Eli Schwartz <[email protected]>
- Loading branch information