macOS: libiconv.2.dyld not loaded #51

New issue

Open

opened 2025-07-29 01:33:51 +00:00 by pauliesnug · 2 comments

pauliesnug commented

2025-07-29 01:33:51 +00:00

After successfully installing Lix with the https://install.lix.systems/lix installation script, I attempted to execute /nix/nix-installer --help and received the error:

/nix/nix-installer 
dyld[PID]: Library not loaded: /nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib
  Referenced from: <DISK-ID> /nix/nix-installer
  Reason: tried: '/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib//libiconv.2.dylib' (no such file)
[1]    PID abort      /nix/nix-installer

My Xcode installation is up to date, I ran brew install libiconv and it was already installed. The dynamic library /nix/store/dka6i6yj8sgws93wc6m0lmqzhk21kq87-libiconv-107/lib/libiconv.2.dylib does exist on initial installation, but the executable seems to be looking for /nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib, which does not exist.

I tested downloading the same executable from the latest lix-installer release: curl -sL -o lix-installer https://install.lix.systems/lix/lix-installer-aarch64-darwin && chmod +x ./lix-installer && ./lix-installer --help and got the same exact error, but if I run curl -sL -o lix-installer https://install.lix.systems/lix && chmod +x ./lix-installer && ./lix-installer --help, allowing the Rustup-based script to download the same exact executable into a tmp folder, it works perfectly and I'm able to manage my installation. Honestly have no idea why this happens.
:3

After successfully installing Lix with the `https://install.lix.systems/lix` installation script, I attempted to execute `/nix/nix-installer --help` and received the error: ```sh /nix/nix-installer dyld[PID]: Library not loaded: /nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib Referenced from: <DISK-ID> /nix/nix-installer Reason: tried: '/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib' (no such file), '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib//libiconv.2.dylib' (no such file) [1] PID abort /nix/nix-installer ``` My Xcode installation is up to date, I ran `brew install libiconv` and it was already installed. The dynamic library `/nix/store/dka6i6yj8sgws93wc6m0lmqzhk21kq87-libiconv-107/lib/libiconv.2.dylib` does exist on initial installation, but the executable seems to be looking for `/nix/store/phzzjrksk8nnmjsbrpbkvv4pr383ab6v-libiconv-109/lib/libiconv.2.dylib`, which does not exist. I tested downloading the same executable from the latest `lix-installer` release: `curl -sL -o lix-installer https://install.lix.systems/lix/lix-installer-aarch64-darwin && chmod +x ./lix-installer && ./lix-installer --help` and got the same exact error, but if I run `curl -sL -o lix-installer https://install.lix.systems/lix && chmod +x ./lix-installer && ./lix-installer --help`, allowing the Rustup-based script to download the same exact executable into a `tmp` folder, it works perfectly and I'm able to manage my installation. Honestly have no idea why this happens. :3

pauliesnug commented

2025-07-29 01:34:57 +00:00

Author

Might be linked to #45

jade commented

2025-08-01 01:54:40 +00:00

Owner

I am very willing to believe this, yes. It would be very plausible that for some reason the binaries we built got linked to something in the nix store, which then led to the sadness observed.

I don't like non-nix environments very much but we might have to go that route to mitigate those issues. agh!

I am very willing to believe this, yes. It would be very plausible that for some reason the binaries we built got linked to something in the nix store, which then led to the sadness observed. I don't like non-nix environments very much but we might have to go that route to mitigate those issues. agh!