On 4/14/2026 2:02 PM, Manuel Jacob wrote:
I added all “build machinery (*.in)” people from MAINTAINERS as CC,
ignoring that some of them didn’t commit anything for a long time.
I’ll also resend a patch series about the *_FOR_BUILD variables (in v1
I forgot to sign off them). These patches are completely unrelated,
apart of being about using environment variables in the build process.
If you think that any of these patches is unsuitable for GCC 16, I can
resend them when GCC 17 stage 1 started.
On 28/03/2026 18.41, Manuel Jacob wrote:
Some of the *_FOR_TARGET environment variables (e.g. CC_FOR_TARGET)
were already preserved because they use the
NCN_STRICT_CHECK_TARGET_TOOLS macro directly. Other *_FOR_TARGET
environment variables (e.g. AS_FOR_TARGET) use the
ACX_CHECK_INSTALLED_TARGET_TOOL macro, which falls back to
NCN_STRICT_CHECK_TARGET_TOOLS but overwrote the environment variable
in some cases before that. E.g. in the case `$build != $host`, the
environment variable was not preserved.
With this patch, each of the *_FOR_TARGET environment variables and
their unsuffixed (“for host”) correspondents are handled consistently
in the sense that a non-empty value takes precedence over:
- cached values
- values inferred by checking for a suitable program in PATH
- tools in the directory passed to --with-build-time-tools (applies
only to *_FOR_TARGET)
Signed-off-by: Manuel Jacob <[email protected]>
I did a spin of this in my tester for sanity's sake and with that clean,
I went ahead and pushed it to the trunk after cobbling together a
ChangeLog entry.
jeff
