!xmLtiCaAJxfhURjrXl:matrix.org

NixOS RISC-V

211 Members
NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux https://github.com/orgs/NixOS/teams/risc-v63 Servers

Load older messages


SenderMessageTime
16 Jul 2025
@dramforever:matrix.orgdramforever get the pkgsCross.riscv64.stdenv.cc package 12:01:11
@dramforever:matrix.orgdramforever riscv64-unknown-linux-gnu-gcc will be right there 12:01:21
@dramforever:matrix.orgdramforever the newlib one is in pkgsCross.riscv64-embedded.stdenv.cc 12:01:34
@winston:milli.ng@winston:milli.ng left the room.13:37:05
17 Jul 2025
@no-mood:matrix.orgno-mood
In reply to @dramforever:matrix.org
get the pkgsCross.riscv64.stdenv.cc package
This is what I needed. I'm still confused as to why it doesn't show up in the Nix package search, given that it's a package
10:49:03
@no-mood:matrix.orgno-mood
In reply to @dramforever:matrix.org
get the pkgsCross.riscv64.stdenv.cc package
*
10:49:13
@dramforever:matrix.orgdramforever under pkgsCross.* is every single package, so for example pkgsCross.riscv64.nano is nano cross compiled to riscv64. if these all showed up in package search you'd never see the second package on package search 10:57:15
@dramforever:matrix.orgdramforeverand, to be honest, pkgsCross isn't well documented. it's more of a hack for convenience than how you set up cross for nixpkgs10:58:50
@dramforever:matrix.orgdramforeversee http://nixos.org/manual/nixpkgs/stable/#sec-cross-usage and my old flake doing cross (OLD! do not use directly) https://github.com/dramforever/nixos-visionfive/blob/907b553bb5ac405f2fa746e7958d634a2b6eb4be/flake.nix#L2511:07:39
@dramforever:matrix.orgdramforever* see http://nixos.org/manual/nixpkgs/stable/#sec-cross-usage and for example my old flake doing cross (OLD! do not use directly) https://github.com/dramforever/nixos-visionfive/blob/907b553bb5ac405f2fa746e7958d634a2b6eb4be/flake.nix#L2511:07:45
@cathal_mullan:matrix.orgCathal joined the room.14:12:21
21 Jul 2025
@zimward:zimward.moezimwardhas anyone run a xianshan nanhu processor? apparently it was taped out in 2023 but i can't find anything that uses it (and can be bought rn)11:08:26
23 Jul 2025
@lotte:chir.rs@lotte:chir.rs changed their profile picture.10:18:20
@implr:hackerspace.plimplr set a profile picture.10:57:49
@implr:hackerspace.plimplr changed their profile picture.11:21:57
24 Jul 2025
@0x4a6f:matrix.org[0x4A6F] New Milk-V Titan announced. 19:38:58
@zimward:zimward.moezimward Compliant with RVA23* (Excluding "V" Extension) lol, so just with hypervisor support 19:49:17
@0x4a6f:matrix.org[0x4A6F] But without full RVA23 features. 19:49:21
@0x4a6f:matrix.org[0x4A6F]Why can't hardware vendors ...19:49:54
@dramforever:matrix.orgdramforevergluten free (except bread)19:50:49
@0x4a6f:matrix.org[0x4A6F]Waiting for something with some juice P870-D in it...19:52:14
@alex:tunstall.xyzAlexIs the RISC-V foundation not policing vendors' use of marketable words?19:53:18
26 Jul 2025
@oak:universumi.fioak changed their profile picture.08:27:15
29 Jul 2025
@plan9better:matrix.orgplan9better joined the room.13:50:51
@rosscomputerguy:matrix.orgTristan Ross Just saw this floating around, more specifically the SoC it uses. Would be cool to run NixOS on it. https://milkv.io/titan 16:40:13
@hexa:lossy.networkhexaRVA23 or else17:28:49
@hexa:lossy.networkhexa

Compliant with RVA23* (Excluding "V" Extension)

17:29:05
@hexa:lossy.networkhexayeah, no.17:29:08
@hexa:lossy.networkhexawas already laughted out of the room here17:30:34
@hexa:lossy.networkhexa* was already laughed out of the room here17:30:58

Show newer messages


Back to Room ListRoom Version: 10