stdenvBootstrapTools: use cctools-port

[reckenrode]

Description of changes

This fixes the Hydra build failure on staging-next. #241951 (comment)

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[tjni]

I have a PR in #243440 addressing this problem in a different way. I don't have a strong opinion on which one we take. Which one do you prefer?

[reckenrode]

I have a PR in #243440 addressing this problem in a different way. I don't have a strong opinion on which one we take. Which one do you prefer?

I don’t feel strongly either way. If your change (presumably using isMachO to test?) produces a working bootstrap tools, it’s probably more forward-looking than continuing to use cctools-port. On the other hand, the stdenv bootstrap starts from cctools-port and builds from there.

[tjni]

I admit I don't know exactly what that bootstrap tools job is testing, but indeed restricting strip and install_name_tool to running only on files that pass isMachO fixes the test locally for me.

[reckenrode]

Closing this since #243440 was merged.