| 4 Apr 2026 |
 Randy Eckenrode | * Building ffmpeg 8 appears to be broken on Darwin. It’s trying to use patchelf ….
> patching script interpreter paths in /nix/store/fvxp6blkrg3h37l348lb4f5aq3v7z67y-ffmpeg-headless-8.0.1
> /nix/store/6ifjywcskbcx5mzy4g1gnygdzgfagfs8-stdenv-darwin/setup: line 267: patchelf: command not found
| 10:53:53 |
| Randy Eckenrode | Oh, wait. That’s my Vulkan patches. That’s my fault. | 10:54:24 |
 antifuchs | Ah, GitHub actions levels of documentation indirection (: | 11:39:40 |
 emily | https://github.com/llvm/llvm-project/compare/llvmorg-21.1.7...llvmorg-21.1.8 | 11:42:16 |
| emily | either one of these or a packaging change | 11:42:34 |
| emily | best guess... https://github.com/llvm/llvm-project/commit/d2e835bd46384aa1628c9d44e3f93438f0795dfd? | 11:43:10 |
| emily | https://github.com/rust-lang/rust/issues/149522 | 11:43:28 |
| emily | would be wild if this somehow broke vim | 11:43:39 |
| emily | try building without optimization? | 11:44:05 |
|  danieroux set a profile picture. | 13:52:43 |
 EsperLily [she/her] | i just tried, setting CFLAGS = -g -O0 and it's still crashing | 20:16:19 |
| emily | try it with -O0 with the old compiler | 20:16:46 |
| emily | since if it is that commit, it'd be an incorrect optimization in LLVM somehow causing it to not crash | 20:17:01 |
| emily | seems bizarre but who knows | 20:17:10 |
| emily | it could ofc be anything else in the stdenv.cc closure too | 20:17:25 |
| emily | (linker stuff…?) | 20:17:38 |
| Randy Eckenrode | Does it crash with LLVM 22? | 20:17:45 |
| EsperLily [she/her] | i'll try that after i do this build with the old compiler | 20:18:13 |
| EsperLily [she/her] | this works fine, no crash | 20:21:40 |
| emily | then I guess it's not https://github.com/llvm/llvm-project/commit/d2e835bd46384aa1628c9d44e3f93438f0795dfd. well, that or your CFLAGS aren't reaching the right part of the build | 20:22:13 |
| emily | I would perhaps try the staging commit immediately before the 21.1.8 merge and the 21.1.8 merge commit itself | 20:22:51 |
| emily | if those differ then it really does have to be something in https://github.com/llvm/llvm-project/compare/llvmorg-21.1.7...llvmorg-21.1.8 somehow | 20:23:20 |
| emily | if not… well, it's a start on bisecting the cycle | 20:23:29 |
| EsperLily [she/her] | i I run path/to/Vim --version it reports its own CFLAGS as being what I set (plus a few -D flags) | 20:26:23 |
| emily | yeah, but maybe it's something other than that binary? dunno | 20:26:48 |
| emily | non-weird possibilities are pretty much eliminated so whatever it is has to be weird in some way | 20:27:02 |
| EsperLily [she/her] | sadly yes | 20:27:51 |
| EsperLily [she/her] | I used final.llvmPackages_22.stdenv and it still crashes | 20:28:02 |
| emily | I think this will be the best next step, since if it narrows it down to that one merge then there's a very short list of commits that could have caused the regression. | 20:32:20 |
| emily | though it seems basically incomprehensible for it to be anything other than the llvm/lib/CodeGen/SelectOptimize.cpp change if it is | 20:33:12 |
