ghc-toolchain followup: Pass user specified options from configure to ghc-toolchain
In !9263 (merged) we introduced the ghc-toolchain
tool to configure target description files, but also generate target description files from configure, which we validate against the ghc-toolchain
ones.
ghc-toolchain
is invoked by ./configure
, however, configure doesn't currently pass the user specified flags (e.g. CFLAGS=...) to ghc-toolchain
. This should be addressed in a followup merge request. (Note that the user doesn't need to know about the existence of ghc-toolchain
, since the configuration interface is still configure
).
The tentative solution is to store all user-specified variables before further configuring them, and passing those user specifications to ghc-toolchain
.
NB: During development in !9263 (merged) we came across multiple tasks and bugs regarding the configuration script. In preparation of merging it, we're opening tickets for the leftover tasks both regarding the new ghc-toolchain
and the toolchain logic in configure
. This is one of those tickets.