In reply to@kity:kity.wtf
maybe i can add llvmPackagesBuildBuild.binutils-unwrapped for (unprefixed, as expected) as

/nix/store/y2bfh2sg9zaw2b6ngbajvjlpnffnj4al-powerpc64le-unknown-linux-musl-clang-wrapper-16.0.6/bin/powerpc64le-unknown-linux-musl-clang -std=gnu99 -o xptcinv>
xpcom/reflect/xptcall/md/unix/xptcstubs_asm_ppc64_linux.o
clang-16: warning: argument unused during compilation: '-pie' [-Wunused-command-line-argument]
clang-16: warning: argument unused during compilation: '-pie' [-Wunused-command-line-argument]
Assembler messages:
Fatal error: invalid listing option `6'
clang-16: error: assembler command failed with exit code 1 (use -v to see invocation)

okay I need help. for context I'm on freebsd, not cross compiled just normal, but I am not sure if that matters here

I tried building gcc: nix-shell -p gcc. The build succeeds, but the cycle checker fails: error: cycle detected in build of '/nix/store/lxbw8ccms1bd9qb4imgnsla5889zvhwp-gcc-12.3.0.drv' in the references of output 'lib' from output 'out'

To the best of my knowledge, the cycle is as follows: gcc-lib/lib/*.so has rpaths for gcc-out/lib, and gcc-out/nix-support/propagated-build-inputs lists gcc-lib. I had my friend build the same setup on linux and the propagated-build-inputs link was still there but the rpath was not. The directory that the rpath points to does not contain any shared objects, so this is probably the link that needs to be broken.

The thing that gets me is that I think the rpath is being set by nixpkgs/pkgs/stdenv/generic/setup.sh: there's an unconditional call to _addRpathPrefix "$out". Assuming I'm understanding correctly, setup.sh is called by the builder used by stdenv.mkDerivation? so this is adding $out/lib to the rpath of everything that gets linked ever. which as I understand is supposed to be okay! like making other outputs which are just symlinks into *-out/lib is supposed to be totally kosher! so then why does the gcc-out derivation explicitly mark a link to gcc-lib? presumably it's to say "okay so if you're trying to depend on me the thing you actually want is over there" but then why does that count for the sake of the cycle checker? idk the whole thing is very confusing.

$ nix path-info -r  $(nix-build -A gcc.cc.lib) |& unnix
/<<NIX>>/libunistring-1.1
/<<NIX>>/libidn2-2.3.4
/<<NIX>>/xgcc-12.3.0-libgcc
/<<NIX>>/glibc-2.37-8
/<<NIX>>/gcc-12.3.0-libgcc
/<<NIX>>/gcc-12.3.0-lib

In reply to@rhelmot:matrix.org
okay okay hang on I can think about this more critically - creating a stdenv for wasi would imply that you had already compiled nix itself for wasi and you wanted to boot nixpkgs under that environment