| 1 Jun 2021 |
 Reventlov | Redacted or Malformed Event | 08:32:35 |
| Reventlov | Redacted or Malformed Event | 08:33:00 |
| Reventlov | Redacted or Malformed Event | 08:33:31 |
 Alyssa Ross | @eelco:nixos.org do you know why i*86 platforms are forced to i686 for the Nix system in configure.ac? | 19:26:04 |
| Alyssa Ross | in #exotic:nixos.org we're wondering what the way to go would be for somebody to build e.g. i486 packages | 19:26:43 |
 niksnut | Dunno, it has been that way for a long time. Probably to avoid getting i786 or whatever. | 20:11:10 |
| niksnut | Oh, here is the explanation:
commit 966bd9d19fb43b6a6022572eb7d80c1e03bfaf3e
Author: Eelco Dolstra <e.dolstra@tudelft.nl>
Date: Fri Aug 13 09:57:51 2004 +0000
* WTF? More canonical system name problems ("athlon-linux" instead of
"i686-linux").
| 20:12:38 |
| Alyssa Ross | ah great, thanks | 20:19:29 |
| Alyssa Ross | I only managed to find the commit from Ludo in 2011 that just said "it's always been this way" | 20:19:42 |
| 2 Jun 2021 |
 Jan Tojnar | Did something change regarding the cycle detection? Now I am getting “error: cycle detected in build of … in the references of output 'lib' from output 'jack'” and the output paths for the cyclic outputs are not in the store, not even with --keep-failed | 01:38:50 |
