#42543 was fixed by unconditionally reading config.mk. However, sometimes this is populated by default values that the user did not give on the command line, for example
CFG_RELEASE_CHANNEL := dev
when running from a location with a .git subdirectory (such as the Debian rustc git repo). This has the effect of rendering the corresponding command-line flags to x.py useless. For example even if I have
[rust]
channel = "stable"
and run
$ ./x.py build --config myconfig.toml
this will get ignored and the value from config.mk (which I did not set) takes precedence.
I can work around this by explicitly passing --release-channel to ./configure but this behaviour does not help rust's overall goal of eventually phasing out this file.
Other flags affected include possibly CFG_PREFIX, but probably not CFG_ENABLE_DEBUGINFO_* as bootstrap/config.rs does not appear to read them.
cc @Mark-Simulacrum
#42543 was fixed by unconditionally reading config.mk. However, sometimes this is populated by default values that the user did not give on the command line, for example
when running from a location with a
.gitsubdirectory (such as the Debian rustc git repo). This has the effect of rendering the corresponding command-line flags tox.pyuseless. For example even if I haveand run
this will get ignored and the value from
config.mk(which I did not set) takes precedence.I can work around this by explicitly passing
--release-channelto./configurebut this behaviour does not help rust's overall goal of eventually phasing out this file.Other flags affected include possibly
CFG_PREFIX, but probably notCFG_ENABLE_DEBUGINFO_*asbootstrap/config.rsdoes not appear to read them.cc @Mark-Simulacrum