Unexpected header file dependencies in later (non CPP) build stage not reported by -M
Building object files with ghc sometimes accesses/depends on various header files that are not reported buy
ghc -M -include-cpp-deps. See this comment for an example. A minimal example would be useful here.
Characterize where these dependencies are coming from, and if they can/should be included in
ghc -M -include-cpp-deps output. In either case, this results in fsatrace lint errors as these dependencies (usually of the form
/include//\*.h) are not tracked by Hadrian. Adding these dependencies to the output of
ghc -M -include-cpp-deps should fix these lint errors, otherwise find another way to resolve the lint errors.
This is a sub-issue of #16400.