Open no92 opened 3 months ago
I understand the reaction to avoid common errors, but this is not something that should be handled in the build system. I suggest making this a disclaimer in the README instead.
Updated the PR with @ArsenArsen's suggestion to use a list of compiler search paths to check against, instead of hardcoding /usr/include
.
We've repeatedly run into people trying to supply their system's
/usr/include
when building a host-mlibc, and it has taken us > 1 question to figure that out; this aims to prevent this common problem.