| 2 Aug 2023 |
 p14 | Interesting to hear that there is a unification effort, that's also good to hear. | 13:34:06 |
 raitobezarius | so any changes that will bring a new discrepancy will probably be delayed because it will introduce more work for that unification stuff | 13:34:09 |
 sorear | iiinteresting | 13:34:28 |
| p14 | Is this effort in a PR or other discussion somewhere? Is there a timeline for it? | 13:35:15 |
| p14 | I may also be interested in helping and testing and whatnot if I get spare bandwidth. | 13:35:42 |
| raitobezarius | (2) I think the timing is complicated, if #246577 is the only change you are hoping to land, I can try to take care of it before going into vacations, but, beyond than that, I think most LLVM maintainers are inactive atm (understandably) | 13:36:22 |
| p14 | I think that's a pretty big step forward in terms of the usability of it. | 13:37:17 |
| raitobezarius | In reply to @p14:matrix.org
I may also be interested in helping and testing and whatnot if I get spare bandwidth. https://github.com/NixOS/nixpkgs/issues/213033 | 13:37:19 |
| raitobezarius | (3) pkgsLLVM is probably low priority and too much to chew for me so at some point, you would have to consider stepping in as a maintainer if you want to see continued stability of that package set | 13:38:14 |
| sorear | would it help if I tested 246577 sooner rather than later? | 13:53:12 |
| p14 | sorear: it would certainly provide more information to me about how well it functions if you want to try and build some other software with it. Feel free to ping me in DMs here (or comment on the PR) as well with any information you glean, though I can't promise to be of much help. | 13:54:08 |
| * raitobezarius nods | 13:59:09 |
| p14 | In reply to @raitobezarius:matrix.org
(3) pkgsLLVM is probably low priority and too much to chew for me so at some point, you would have to consider stepping in as a maintainer if you want to see continued stability of that package set On this point Iβm happy to try and provide some input and testing; I have the capability to bisect to find issues and may be able to provide a small amount of personal effort to dig into issues to try and keep it working. | 15:12:27 |
| 3 Aug 2023 |
|  @yvtjp:matrix.org changed their profile picture. | 10:28:14 |
|  Lotte (it/its)/Cinny (she/her) ΞΈΞ& changed their profile picture. | 12:57:46 |
|  ynewmark joined the room. | 15:01:55 |
| 4 Aug 2023 |
|  ius joined the room. | 15:34:07 |
|  π@crystallinefire:chat.solarpunk.moe joined the room. | 20:07:40 |
|  lord_fomo joined the room. | 20:11:16 |
| 9 Aug 2023 |
|  Steven Keuchel joined the room. | 17:40:38 |
| 10 Aug 2023 |
|  pbsds changed their display name from pbsds (UTC+1) to pbsds. | 14:54:47 |
| 13 Aug 2023 |
|  @10leej:matrix.org joined the room. | 01:24:45 |
| 15 Aug 2023 |
| @10leej:matrix.org left the room. | 19:34:03 |
| 16 Aug 2023 |
|  rhelmot joined the room. | 05:49:49 |
| rhelmot | Hi! I'm trying to revive the FreeBSD nix/nixpkgs support. I've gotten as far as being able to compile moderately interesting packages with the bootstrap compiler (FreeBSD-native clang), but when I try to build gcc everything falls apart and I think it's me doing something wrong with the stdenv. Is this the right place to ask for help with that? | 05:55:34 |
| π@crystallinefire:chat.solarpunk.moe | oooh i want to help with that | 05:55:59 |
| π@crystallinefire:chat.solarpunk.moe | this seems like the right place to me | 05:56:07 |
| rhelmot | nice! Okay, I'll make what I have presentable and I can show it to you. | 05:56:31 |
| rhelmot | https://github.com/rhelmot/nixpkgs/compare/freebsd%7E%7E...rhelmot:nixpkgs:freebsd | 06:11:11 |
| rhelmot | The first commit is where I got as far as I could with the native compiler. the second commit is where I attempted to do the full bootstrap | 06:11:27 |
