| 24 Jan 2025 |
 kuruczgy | And it seems there is a fix already: https://github.com/NixOS/nixpkgs/pull/375953
I should be able to just grab that, I am already patching nixpkgs in my project with some other stuff anyway... | 12:09:58 |
| 28 Jan 2025 |
|  Thomas m changed their display name from howlymowly to Thomas m. | 19:26:47 |
| 29 Jan 2025 |
|  Kira joined the room. | 00:20:03 |
| 30 Jan 2025 |
|  laurynasp joined the room. | 08:54:24 |
| 31 Jan 2025 |
|  SomeoneSerge (matrix works sometimes) changed their display name from SomeoneSerge to SomeoneSerge (Bruxelles). | 19:31:59 |
| 2 Feb 2025 |
|  thomasjm joined the room. | 13:08:37 |
|  pbsds changed their display name from pbsds to pbsds (FOSDEM). | 16:04:51 |
 K900 | Should probably post here too | 19:16:28 |
| K900 | https://github.com/NixOS/nixpkgs/pull/378569 | 19:16:29 |
| K900 | Changes how our GCC is built somewhat significantly | 19:16:38 |
| K900 | Please try it on more exotic targets | 19:16:43 |
 Tristan Ross | Sweet, does it effect just GCC or does it also effect gfortran? | 19:21:26 |
| Tristan Ross | Oh, at a glance it looks like it wouldn't fix my problem with pkgsLLVM.gfortran | 19:22:40 |
| K900 | It is unlikely to | 19:26:44 |
| K900 | The ideal effect of it is that absolutely nothing observably changes | 19:26:55 |
| Tristan Ross | Oh fun. | 19:35:31 |
| Tristan Ross | I still hope we can get https://github.com/NixOS/nixpkgs/issues/374950 fixed. I tried looking at it but idk what's going on in GCC. | 19:40:41 |
| 3 Feb 2025 |
| SomeoneSerge (matrix works sometimes) changed their display name from SomeoneSerge (Bruxelles) to SomeoneSerge (Gand St. Pieters). | 13:38:41 |
|  @niclasoverby:beeper.com joined the room. | 13:47:54 |
| pbsds changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:48 |
| 4 Feb 2025 |
 linj | My client tells me that this room has no name. I guess this is the cross room. Could you me an example of checkInputs? Is it something that is needed when the built package runs tests outside of nix build sandbox? | 02:12:28 |
| linj | * Element tells me this room has no name. I guess this is the cross compilation room. Could you me an example of checkInputs? Is it something that is needed when the built package runs tests outside of nix build sandbox? | 02:13:51 |
| linj | * Element tells me this room has no name. I guess this is the cross compilation room. Could you give me an example of checkInputs? Is it something that is needed when the built package runs tests outside of nix build sandbox? | 02:14:25 |
| linj | Another question: package foo runs itself in the checkPhase and it looks up bar from PATH and calls bar. Is bar a checkInputs or nativeCheckInputs? | 02:20:19 |
| linj | * Another question: package foo runs itself in its checkPhase. During the checkPhase of foo, it looks up bar from PATH and calls bar. Is bar a checkInputs or nativeCheckInputs of foo? | 02:21:34 |
 Artturin | @me:linj.tech: checkInputs and nativeCheckInputs work the same as buildInputs and nativeBuildInputs | 02:49:45 |
| Artturin | In reply to @me:linj.tech
Another question: package foo runs itself in its checkPhase. During the checkPhase of foo, it looks up bar from PATH and calls bar. Is bar a checkInputs or nativeCheckInputs of foo? The test wouldn't work/run when cross compiling to a platform which build can't exec | 02:51:13 |
| Artturin | But it would be nativeBuildInputs | 02:51:20 |
| Artturin | * But it would be nativeCheckInputs | 02:51:30 |
| Tristan Ross | checkInputs could be something like a library needed to make a test work | 02:59:51 |
