Wow, this is unfortunate. If I build:

nix build --rebuild pkgsLLVM.llvmPackages_15.compiler-rt-no-libc.stdenv.cc.bintools```

I get:

-r--r--r-- 1 root root 0 Jan 1 1970 result/nix-support/setup-hook

Now if I try to determine _why_ setup-hook is empty by setting the preHook to include 'set -x', then, it's non-empty and works correctly:

preHook = if bintoolsName == "llvm-binutils" then "set -x" else null;

I end up with:

-r--r--r-- 1 root root 4781 Jan 1 1970 result/nix-support/setup-hook

What's going on?

Wow, this is unfortunate. If I build:

nix build --rebuild pkgsLLVM.llvmPackages_15.compiler-rt-no-libc.stdenv.cc.bintools
```
I get:

-r--r--r-- 1 root root 0 Jan 1 1970 result/nix-support/setup-hook

Now if I try to determine _why_ setup-hook is empty by setting the preHook to include 'set -x', then, it's non-empty and works correctly:

preHook = if bintoolsName == "llvm-binutils" then "set -x" else null;

I end up with:

-r--r--r-- 1 root root 4781 Jan 1 1970 result/nix-support/setup-hook

What's going on?

Wow, this is unfortunate. If I build:

nix build --rebuild pkgsLLVM.llvmPackages_15.compiler-rt-no-libc.stdenv.cc.bintools

I get:

-r--r--r-- 1 root root 0 Jan  1  1970 result/nix-support/setup-hook

Now if I try to determine why setup-hook is empty by setting the preHook to include 'set -x', then, it's non-empty and works correctly:

preHook = if bintoolsName == "llvm-binutils" then "set -x" else null;

I end up with:

-r--r--r-- 1 root root 4781 Jan  1  1970 result/nix-support/setup-hook

What's going on?

In reply to @p14:matrix.org
I guess I'm seeing: https://github.com/NixOS/nixpkgs/blob/2283bf968f3b6a2f100d81fb43db6d91f6aea706/pkgs/stdenv/generic/setup.sh#L936

On my machine,

nix build --rebuild nixpkgs/73f18ca8b33ad1281958193e7e35f63b6ef47e52#pkgsLLVM.llvmPackages_15.compiler-rt-no-libc.stdenv.cc.bintools
stat -c%s result/nix-support/setup-hook
``
Apparently, with --rebuild, reproducibly gives me a zero-byte setup-hook. But not on another machine. So, nondeterminism lurking somewhere nasty?

On my machine,

nix build --rebuild nixpkgs/73f18ca8b33ad1281958193e7e35f63b6ef47e52#pkgsLLVM.llvmPackages_15.compiler-rt-no-libc.stdenv.cc.bintools
stat -c%s result/nix-support/setup-hook

Apparently, with --rebuild, reproducibly gives me a zero-byte setup-hook. But not on another machine. So, nondeterminism lurking somewhere nasty?

I'm afraid that if I simply delete the bad paths I won't be able to reproduce this. Though I dare say that keeping the bad outputs doesn't help me much either.

That said, I'm doing a --rebuild, that shouldn't keep corrupted paths on disk would it? This means surely that I'm repeatably generating the bad file, (I hope, tell me if I'm wrong?)

Build logs appear the same.

x86_64-unknown-linux-gnu-llvm-binutils-wrapper> unpacking sources
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> patching sources
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> updateAutotoolsGnuConfigScriptsPhase
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> installing
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> post-installation fixup
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> shrinking RPATHs of ELF executables and libraries in /nix/store/9kaazhysw3pmzlrslpb1nsgy97hq8hlm-x86_64-unknown-linux-gnu-llvm-binutils-wrapper-15.0.7
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> checking for references to /build/ in /nix/store/9kaazhysw3pmzlrslpb1nsgy97hq8hlm-x86_64-unknown-linux-gnu-llvm-binutils-wrapper-15.0.7...
x86_64-unknown-linux-gnu-llvm-binutils-wrapper> patching script interpreter paths in /nix/store/9kaazhysw3pmzlrslpb1nsgy97hq8hlm-x86_64-unknown-linux-gnu-llvm-binutils-wrapper-15.0.7