ris has quit [Ping timeout: 258 seconds]
disasm| has quit [Quit: WeeChat 2.0]
disasm has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 244 seconds]
nD5Xjz has joined #nix-darwin
abathur has quit [Ping timeout: 244 seconds]
sivteck has joined #nix-darwin
sivteck has left #nix-darwin [#nix-darwin]
philr has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 268 seconds]
nD5Xjz has joined #nix-darwin
nD5Xjz_ has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 268 seconds]
copumpkin has joined #nix-darwin
arahael has quit [Quit: WeeChat 2.2]
nD5Xjz has joined #nix-darwin
nD5Xjz_ has quit [Ping timeout: 246 seconds]
nD5Xjz has quit [Ping timeout: 272 seconds]
nD5Xjz has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 246 seconds]
nD5Xjz has joined #nix-darwin
Enzime has quit [Ping timeout: 245 seconds]
<dhess> matthewbauer: re: https://github.com/NixOS/nixpkgs/issues/61596, how can I track down which libdispatch the Emacs executable is linked to?
<{^_^}> #61596 (by dhess, 1 week ago, open): emacsMacport crashes on start with new Darwin stdenv
<dhess> I thought it was odd that the stack trace was exactly the same, makes me wonder if I missed something and somehow built it against the old libdispatch
<dhess> normally I use otool for this but I couldn't find libdispatch in there at all. Maybe it's wrapped up in a framework? I'm not sure how this works with macOS and Nixpkgs.
<matthewbauer> yeah we just use the headers for libdispatch, so that's not unexpected
<matthewbauer> i was hoping it was just a changed api
<dhess> ahh
<dhess> that makes more sense now
<cbarrett> LnL: bumped it down to 1 and it was still erroring in the same way :(
<LnL> hmm, what about increasing the number of users in the vm?
<LnL> the nix installer also creates more than necessary to avoid issues like this
* LnL back in a few hours
kraem has joined #nix-darwin
philr has quit [Ping timeout: 248 seconds]
kyren has joined #nix-darwin
<cbarrett> LnL: Not sure how to do that, need to take a look at how it's set up