Pass user-specified options to ghc-toolchain
The current user interface to configuring target toolchains is `./configure`. In !9263 we added a new tool to configure target toolchains called `ghc-toolchain`, but the blessed way of creating these toolchains is still through configure. However, we were not passing the user-specified options given with the `./configure` invocation to the ghc-toolchain tool. This commit remedies that by storing the user options and environment variables in USER_* variables, which then get passed to GHC-toolchain. The exception to the rule is the windows bundled toolchain, which overrides the USER_* variables with whatever flags the windows bundled toolchain requires to work. We consider the bundled toolchain to be effectively the user specifying options, since the actual user delegated that configuration work. Closes #23678
Showing
- configure.ac 13 additions, 0 deletionsconfigure.ac
- m4/fp_cpp_cmd_with_args.m4 1 addition, 0 deletionsm4/fp_cpp_cmd_with_args.m4
- m4/fp_hs_cpp_cmd_with_args.m4 1 addition, 0 deletionsm4/fp_hs_cpp_cmd_with_args.m4
- m4/fp_setup_windows_toolchain.m4 9 additions, 0 deletionsm4/fp_setup_windows_toolchain.m4
- m4/ghc_toolchain.m4 24 additions, 0 deletionsm4/ghc_toolchain.m4
- utils/ghc-toolchain/src/GHC/Toolchain/Tools/Cc.hs 1 addition, 15 deletionsutils/ghc-toolchain/src/GHC/Toolchain/Tools/Cc.hs
Loading
Please register or sign in to comment