| 2 Feb 2025 |
 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 |
| linj | I know that. It is just a bit confusing when build = host for cases like foo. | 02:59:59 |
| Tristan Ross | Versus nativeCheckInputs could be like a test runner framework that's necessary to run | 03:00:12 |
| Tristan Ross | I'd say it really depends on the package and what cross means in this sense | 03:00:33 |
| Tristan Ross | Because technically pkgsLLVM is cross | 03:00:43 |
| Tristan Ross | But it is still native. | 03:00:51 |
| Artturin | In reply to @rosscomputerguy:matrix.org
But it is still native. It's build canExecute host cross | 03:01:23 |
| linj | but when build != host, you cannot run the link result in checkPhase, right? | 03:01:49 |
| Artturin | In reply to @me:linj.tech
but when build != host, you cannot run the link result in checkPhase, right? You can if build canExecute host | 03:02:10 |
| Tristan Ross | Ish, like what Artturin mentioned. Maybe there's a package out there which builds for host but builds tests for build. | 03:02:56 |
| linj | Oh, TIL, it is possible that build canExecute host even if build != host | 03:04:16 |
| linj | thanks | 03:05:04 |
|  Axman6 joined the room. | 05:55:14 |
| linj | h0 + t1 in {-1, 0, -1} looks like a typo. I guess it should be h0 + t1 in {-1, 0, 1} | 08:20:19 |
