Skip to content

bindist `configure` script uses different tool variables than source `configure`

Summary

As evidenced here, the source configure script uses environment variables INSTALL_NAME_TOOL and OTOOL but the bindist configure script uses InstallNameToolCmd and OtoolCmd instead, respectively.

Steps to reproduce

  1. export OTOOL=/nix/store/vpnp0c420cjmx82g05jq3nm5skdrblvk-cctools-binutils-darwin-16.0.6-973.0.1/bin/otool
  2. ./configure && build/hadrian -j binary-dist-dir
  3. ( cd _build/bindist/* && ./configure && make lib/settings )
$ grep otool _build/stage?/lib/settings
_build/stage0/lib/settings:,("otool command", "/nix/store/vpnp0c420cjmx82g05jq3nm5skdrblvk-cctools-binutils-darwin-16.0.6-973.0.1/bin/otool")
_build/stage1/lib/settings:,("otool command", "/nix/store/vpnp0c420cjmx82g05jq3nm5skdrblvk-cctools-binutils-darwin-16.0.6-973.0.1/bin/otool")

$ grep otool _build/bindist/*/lib/settings
,("otool command", "otool")

Expected behavior

The bindist configure script should behave similar to the main configure script and not use different variables.

Environment

  • GHC version used: 9.6.3

Optional:

  • Operating System: darwin
  • System Architecture: aarch64, x86_64
Edited by Claudio Bley
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information