| 28 Apr 2026 |
 zoë (@blokyk) | (just a guess, plus i'm not sure how flakes interact with toString ./foo since i never use flakes) | 13:19:17 |
 antifuchs | yeah, that could explain why interpolating the path in a string correctly does the thing | 13:19:27 |
| antifuchs | * yeah, that could explain why interpolating the path in a string correctly fails | 13:19:43 |
| zoë (@blokyk) | yeah that's also definitely it then | 13:19:51 |
| zoë (@blokyk) | ...now to find the toString responsible for it x) | 13:20:02 |
| zoë (@blokyk) | * ...now good luck findign the toString responsible for it x) | 13:20:12 |
| zoë (@blokyk) | * ...now good luck finding the toString responsible for it x) | 13:20:16 |
| antifuchs | :lmaohno: | 13:20:23 |
| zoë (@blokyk) | probably just need to change these lines | 13:28:04 |
| zoë (@blokyk) | (i can't test it (and don't know how to use that software anyway), but you might want to try that antifuchs (e.g. by disabling the original module and then importing your patched version) and then submit a PR) | 13:30:24 |
| zoë (@blokyk) | * (i can't test it (and don't know how to use that software anyway, so qemu vm won't help), but you might want to try that antifuchs (e.g. by disabling the original module and then importing your patched version) and then submit a PR) | 13:30:53 |
| antifuchs | thank you! that definitely seems like the place to start | 13:31:27 |
| antifuchs | (also, huh, I didn't know about disabledModules, that will come in super handy) | 13:43:21 |
| zoë (@blokyk) | haha yeah i learned about it during my darkest hours and it was very very useful (which is part of why i wrote that message with that link, because i wanted to spread the word :) | 13:44:10 |
| antifuchs | "oh good", the paths get converted to strings before that code even gets to them. guess this is buried deeper. | 14:38:19 |
| antifuchs | * "oh good", the paths get converted to strings before that code even gets to them. guess this is buried deeper. no wait the module doesn't actually get disabled | 14:40:51 |
| antifuchs | yuuuup the function you identified was exactly it; using string interpolation on the path instead of toString on paths correctly fails the build, now that I'm doing the module-replacement right. | 14:55:22 |
| zoë (@blokyk) | maybe i'm just blind, but is there any instruction for building lix with debug symbols? i tried to debug it with lldb and i just get nothing ^^; | 16:29:12 |
| zoë (@blokyk) | * maybe i'm just blind, but is there any instruction for building lix with debug info? i tried to debug it with lldb and i just don't get any source ^^; | 16:35:41 |
| zoë (@blokyk) | hmm actually it's just that every source path is pointing to /build/lix instead of /lix | 16:42:55 |
| zoë (@blokyk) | * nvm it's just that every source path is pointing to /build/lix instead of /lix | 16:43:16 |
 Qyriad | This is a persistent problem we have with everything we build that doesn't substitute from Nixpkgs (where nixseparatedebuginfod works) >.> | 16:44:34 |
| 29 Apr 2026 |
| antifuchs | to close the loop, here | 13:54:38 |
| antifuchs | * to close the loop, I think I fixed the thing https://github.com/NixOS/nixpkgs/pull/514441 | 13:54:48 |
| zoë (@blokyk) | actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb; is there some nuance i'm missing there? | 15:12:57 |
| zoë (@blokyk) | * actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb without needing any setup in the debugger (eg source-map in lldb); is there some nuance i'm missing there? | 15:13:45 |
| zoë (@blokyk) | * actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb without needing any setup in the debugger (eg source-map in lldb); is there some nuance i'm missing there? | 15:13:52 |
| 30 Apr 2026 |
|  @deezrightwinger:matrix.org joined the room. | 01:21:10 |
| @deezrightwinger:matrix.org | Your tos is a hoot | 01:21:24 |
 electria | I didn't know Lix had a Terms of Service (TOS), considering it's not a service...
A development chat is also most certainly not the right place for this
| 01:27:31 |
