andremedeiros has quit [Read error: Connection reset by peer]
andremedeiros has joined #nix-darwin
<plumm>
LnL llvm 12 soon
hedgie has quit []
hedgie has joined #nix-darwin
eraserhd3 has joined #nix-darwin
eraserhd2 has quit [Ping timeout: 260 seconds]
stephank has quit [Quit: stephank]
stephank has joined #nix-darwin
mog has quit [Ping timeout: 246 seconds]
mog has joined #nix-darwin
siraben has quit [Ping timeout: 248 seconds]
__monty__ has joined #nix-darwin
siraben has joined #nix-darwin
andremedeiros has quit [Quit: ZNC 1.8.2 - https://znc.in]
andremedeiros has joined #nix-darwin
<__monty__>
LnL: Hmm, so I've merged your LLVM bump branch into mine, plan to bump further to LLVM 11. Running into problems with all the bootstrap tools though, like fetchurl and zlib. They use `stdenv.cc` which is set to `/dev/null` in the darwin stdenv stage 0.
<__monty__>
Does this sound familiar? I'm a bit surprised no one else would've run into this before so I suspect I must be doing something wrong.
philr has quit [Ping timeout: 240 seconds]
<__monty__>
Seems to have mostly been because I was mixing llvmPackages_7 and 9, occurrences have been added since your branch.
<__monty__>
I patched the check to default to false.
<LnL>
check?
<__monty__>
stdenv.cc being a string was making checks in the bootstrap utilities fail. Like "stdenv.cc.isGNU" in fetchurl.
<LnL>
hmm, that's odd that's how it works currently
<__monty__>
Oh, no. I didn't have to patch the check. It was because occurrences of llvmPackages_7 have been added since you branched so those weren't altered by the merge. Mixing those versions is what caused the problems with bootstrap utilities.
<LnL>
ah yeah, kind of annoying but al the roots of things used in the stdenv need to be replaced with bootstrap dummys
<LnL>
which means we need to use the correct versions in a bunch of places there
<LnL>
btw that bootstrap tools bump probably isn't relevant anymore since it's been updated since
<__monty__>
Oh, so I should just use my own patched bootstrapFiles tarball?
<LnL>
actually, the updated one is still llvm7 so might still cause the same issues