| 11 Feb 2025 |
|  test 🏳️⚧️ joined the room. | 01:41:18 |
| 15 Feb 2025 |
|  Crower joined the room. | 00:35:03 |
|  BenjB83 joined the room. | 10:16:28 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:00 |
| 17 Feb 2025 |
|  Marcus changed their profile picture. | 21:38:07 |
| 18 Feb 2025 |
|  Leon joined the room. | 23:01:33 |
| Leon | I've been tuned out of this for a long time, but I recall there being some discussions about trying to pool together some native riscv64 builders in the past, did that lead anywhere?
This issue seems to have gone dry some time ago: https://github.com/nix-community/infra/issues/715
Scrolling up Tristan Ross you seem to be doing native riscv64 compiles, is that using actual hardware or QEMU? | 23:04:52 |
 Tristan Ross | In reply to @leons:is.currently.online
I've been tuned out of this for a long time, but I recall there being some discussions about trying to pool together some native riscv64 builders in the past, did that lead anywhere?
This issue seems to have gone dry some time ago: https://github.com/nix-community/infra/issues/715
Scrolling up Tristan Ross you seem to be doing native riscv64 compiles, is that using actual hardware or QEMU? I do real hardware | 23:05:24 |
| Leon | Oh wow, that's cool. Is that a small SBC or some larger system? Do you have some more details on your setup somewhere? | 23:06:12 |
| Tristan Ross | VisionFive2 | 23:06:26 |
| Tristan Ross | I'm still trying to get NixOS installed on it, the initrd can't find my NVME | 23:06:49 |
| Leon | Gotcha. Yeah, I have one of those, 2 BeagleV Ahead, a couple smaller Milk-V targets and just got the Framework RISC-V Mainboard. So it's not much, but was wondering whether I can throw these boards into a corner in my Uni's lab and have them do something more useful than collect dust until I or someone else finds out how to get NixOS running on the Framework mainboard haha | 23:08:31 |
| Tristan Ross | Yeah, most systems use the JH7110 which isn't that powerful lol | 23:08:54 |
| Leon | Right right. | 23:09:01 |
| Tristan Ross | There's the newer P550 but the price | 23:09:04 |
| Leon | FWIW, I'm running the pre-built Fedora 41 image on the Framework mainboard right now, and running GNOME + Firefox, listening to music, etc. is somewhat usable. Definitely better than what I remember from my VF2 | 23:10:41 |
| Leon | (I don't know how much frequency scaling this thing does, could thermals have an impact?) | 23:11:08 |
| Tristan Ross | That silicon is probably more mature than the one I've got | 23:11:19 |
| Tristan Ross | The VF2 is older so I wouldn't doubt the Framework being more mature | 23:11:36 |
| Tristan Ross | I've ran into some oddities in my VF2 like NIC DMA not working | 23:11:59 |
| Leon | Well they both use the JH7110 SoC, so shouldn't be much of a difference I guess. | 23:12:27 |
| Tristan Ross | Yeah but the rest of the board matters too | 23:12:45 |
| Tristan Ross | And it's possible there's different revisions | 23:12:55 |
| Leon | But it sounds like there's not yet a Hydra or something I could hook this up to? | 23:13:49 |
| Tristan Ross | Not currently | 23:13:56 |
| Tristan Ross | @matthewcroughan:defenestrate has floated the idea | 23:14:35 |
| Leon | Cool, excited to maybe build something. | 23:16:19 |
| 19 Feb 2025 |
 [0x4A6F] | I got a Milk-V Megrez waiting for me to have time working on it... | 00:01:19 |
| 21 Feb 2025 |
| Tristan Ross | procmail-riscv64-linux> Whoeaaa! This actually can't happen.
procmail-riscv64-linux> You have a look and see if you detect anything uncanny:
procmail-riscv64-linux> *******************************************************
procmail-riscv64-linux> _autotst.c: In function 'main':
procmail-riscv64-linux> _autotst.c:110:9: warning: ignoring return value of 'setgid' declared with attribute 'warn_unused_result' [-Wunused-result]
procmail-riscv64-linux> 110 | { setgid(2);
procmail-riscv64-linux> | ^~~~~~~~~
procmail-riscv64-linux> _autotst.c:114:12: warning: ignoring return value of 'setuid' declared with attribute 'warn_unused_result' [-Wunused-result]
procmail-riscv64-linux> 114 | { setuid(2);
procmail-riscv64-linux> | ^~~~~~~~~
procmail-riscv64-linux> _autotst.c:127:12: warning: ignoring return value of 'setegid' declared with attribute 'warn_unused_result' [-Wunused-result]
procmail-riscv64-linux> 127 | { setegid(groups[i]);
procmail-riscv64-linux> | ^~~~~~~~~~~~~~~~~~
procmail-riscv64-linux> _autotst.c:145:6: warning: ignoring return value of 'chown' declared with attribute 'warn_unused_result' [-Wunused-result]
procmail-riscv64-linux> 145 | chown(argv[1],2,getegid());setuid(2); /* adjust the directory first */
procmail-riscv64-linux> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
procmail-riscv64-linux> _autotst.c:145:33: warning: ignoring return value of 'setuid' declared with attribute 'warn_unused_result' [-Wunused-result]
procmail-riscv64-linux> 145 | chown(argv[1],2,getegid());setuid(2); /* adjust the directory first */
procmail-riscv64-linux> | ^~~~~~~~~
procmail-riscv64-linux> *******************************************************
procmail-riscv64-linux> I suggest you take a look at the definition of LDFLAGS*
procmail-riscv64-linux> in the Makefile before you try make again.
procmail-riscv64-linux> make[1]: *** [Makefile:124: ../autoconf.h] Error 1
procmail-riscv64-linux> make[1]: Leaving directory '/build/procmail-3.24/src'
procmail-riscv64-linux> make: *** [Makefile:155: autoconf.h] Error 2
procmail fails to build in a funny way
| 17:49:05 |
| Tristan Ross | Looks to be the same as https://github.com/NixOS/nixpkgs/issues/334916 | 17:58:10 |
