| 12 Dec 2024 |
 Tristan Ross | I thought I fixed it months ago | 18:26:10 |
 Artturin | yep https://github.com/NixOS/nixpkgs/pull/348676 | 18:26:37 |
 truby | I did see a patch to upgrade to gettext 0.22 which should have fixed it, but my graph still pulls in 0.21 | 18:27:29 |
| Artturin | Now it's fixed without the patch https://github.com/NixOS/nixpkgs/pull/358254 patch removed in https://github.com/NixOS/nixpkgs/pull/360044 | 18:28:50 |
| Artturin | 0.22.5 | 18:28:55 |
| Tristan Ross | Make sure you're on the right nixpkgs | 18:29:14 |
| truby | I did a nix flake update right before trying the build | 18:29:27 |
| Tristan Ross | What's your nixpkgs git rev? | 18:29:47 |
| truby | I'll have to get back to you on that, I'm not on my nixos machine rn 😅 | 18:30:06 |
| truby | Tristan Ross: on an unrelated note while you're here (since you look like the person to ask about Nix LLVM?) do you know if anyone has tried packaging flang? Asking because I'm happy to have a look at it/help out with it not because I actually need it for anything (I work on flang for my day job 😰) | 18:32:02 |
| Tristan Ross | I'm not familiar with flang at all | 18:32:45 |
| Tristan Ross | I might look into it after the LLVM libc PR is merged | 18:32:57 |
| truby | I don't think it should be too hard; I think you can just wrap it in exactly the same way as clang as all the driver options should be the same. We didn't support -B last time I tried to look at it, if that's still the case I'm happy to add that from the flang side | 18:34:10 |
| Tristan Ross | Maybe, we'll have to see. | 18:35:19 |
| truby | I'm not sure how many of the hardening flags we have either; or how many of them make sense for Fortran. | 18:35:43 |
| Artturin | truby: https://github.com/search?q=lang%3Anix%20%2Fflang%2F&type=code | 18:35:56 |
| Tristan Ross | Also, my CPU model PR I might close and redo completely. I have better ideas as to handling it. | 18:36:40 |
| truby | as another unrelated question; do you know if there's a better solution for having a dev environment for working on LLVM than just using fhsEnv? So that the clang you build in the dev shell can actually find libc etc? Atm I'm just shoving everything in a fhsEnv but it feels kinda hacky. | 18:37:30 |
| Tristan Ross | Check the wiki | 18:37:49 |
| Tristan Ross | I've done nix develop nixpkgs#llvmPackages.clang | 18:38:16 |
| Tristan Ross | And that's worked before. | 18:38:22 |
| truby | I tried what was on the wiki and it didn't work for some reason, but now that I think of it that might have been flang not supporting -B... :) | 18:38:52 |
| truby | guess that's on me to fix if it's still true... | 18:39:50 |
| truby | I think most of these are referring to "classic" flang, which is a completely different compiler with the same name. It's not at all confusing and never causes any issues for us. 😃 | 18:40:41 |
 p14 | In reply to @rosscomputerguy:matrix.org
And that's worked before. That's fine for building clang, but if you subsequently try to use the built clang, it won't work well because it's not wrapped. | 19:22:21 |
| p14 | I'm not sure I've seen nixpkgs have a good answer to this. I think what's needed is a way of dumping the flags needed somewhere (e.g. to find the C/C++ stdlib) that the development compiler can pick up. My method is to use NIX_DEBUG on some other compiler and dump them into a clang{,++}.cfg next to my development compiler. | 19:23:28 |
| p14 | Which is a little fragile since there aren't GC roots for those references, but it seems to work well enough for my purposes as a development environment. | 19:23:56 |
 Philip Taron (UTC-8) | I filled it in. Did you see the draft I posted earlier? | 19:45:57 |
 Randy Eckenrode | I need to add my availability, though it’s probably a bit limited. | 19:46:53 |
| Tristan Ross | What draft? | 19:55:09 |
