nixpkgs-suyu/pkgs/build-support/cc-wrapper/fortran-hook.sh

getTargetRole
getTargetRoleWrapper

export FC${role_post}=@named_fc@

# If unset, assume the default hardening flags.
: ${NIX_HARDENING_ENABLE="@default_hardening_flags_str@"}
export NIX_HARDENING_ENABLE

unset -v role_post
cc-wrapper: set FC when langFortran is on We need to set FC so that CMake and other tools can find the fortran compiler. Also we need to limit the hardening flags since fortify and format don’t work with fortran. Fixes #88449 2020-07-06 06:22:19 +02:00			`getTargetRole`
			`getTargetRoleWrapper`

			`export FC${role_post}=@named_fc@`

			`# If unset, assume the default hardening flags.`
mkDerivation, bintools-wrapper: move defaultHardeningFlags determination to bintools-wrapper this makes it a lot easier to create a modified stdenv with a different set of defaultHardeningFlags and as a bonus allows us to inject the correct defaultHardeningFlags into toolchain wrapper scripts, reducing repetition. while most hardening flags are arguably more of a compiler thing, it works better to put them in bintools-wrapper because cc-wrapper can easily refer to bintools but not vice-versa. mkDerivation can still easily refer to either when it is constructed. this also switches fortran-hook.sh to use the same defaults for NIX_HARDENING_ENABLE as for C. previously NIX_HARDENING_ENABLE defaults were apparently used to avoid passing problematic flags to a fortran compiler, but this falls apart as soon as mkDerivation sets its own NIX_HARDENING_ENABLE - cc.hardeningUnsupportedFlags is a more appropriate mechanism for this as it actively filters out flags from being used by the wrapper, so switch to using that instead. this is still an imperfect mechanism because it doesn't handle a compiler which has both langFortran and langC very well - applying the superset of the two's hardeningUnsupportedFlags to either compiler's invocation. however this is nothing new - cc-wrapper already poorly handles a langFortran+langC compiler, applying two setup hooks that have contradictory options. 2023-10-02 20:38:56 +02:00			`: ${NIX_HARDENING_ENABLE="@default_hardening_flags_str@"}`
cc-wrapper: set FC when langFortran is on We need to set FC so that CMake and other tools can find the fortran compiler. Also we need to limit the hardening flags since fortify and format don’t work with fortran. Fixes #88449 2020-07-06 06:22:19 +02:00			`export NIX_HARDENING_ENABLE`

			`unset -v role_post`