<stephank>
Meh, turns out chroot is probably more difficult on Big Sur, if anything. Shared cache isn't magically available, it's just large files in /System/Library/dyld. I was thinking, hard links maybe, but appears they don't work across APFS volumes (system stuff is a separate volume).
<stephank>
Would be cool if we could create firmlinks beyond /etc/synthetic.conf. That'd be like bind mounts. :)
xcmw has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<stephank>
Hah, creating a copy of the shared cache appears to hang stuff for a bit. Maybe signature validation? But after that: dyld: dyld cache load error: syscall to map cache into shared region failed
<stephank>
I think it still does fallback, and if so, it could theoretically work with the original libraries in place. But not going to bother. :)
<LnL>
synthetic.conf doesn't create firmlinks, but yeah from what I understant those give similar functionality to bind mounts
<LnL>
btw doesn't the linker cache stuff happen in a daemon?
<stephank>
I haven't seen any mention of a daemon. It looks like it's just a big memory mapped file. There used to be a tool `update_dyld_shared_cache`, which I think rebuilds that file, but here on Big Sur that just prints: "This tool is deprecated."
<LnL>
I don't remember the details, maybe I'm just thinking of dyld3 which added the cache