| 24 May 2022 |
Rick (Mindavi) | Qemu x 32 | 15:32:30 |
j-k | 3 failed tests on bison | 15:41:07 |
| 25 May 2022 |
Alyssa Ross | Ericson2314: I'm looking at https://github.com/NixOS/nixpkgs/pull/169793 again. I think to do this properly we need to change the release.nix infrastructure to just use full triples everywhere. But that's going to be a huge amount of work, so I think I'm going to have to try to split it up. | 10:34:27 |
John Ericson | Alyssa Ross: yeah I see | 13:50:09 |
John Ericson | that change sounds good to me! | 13:50:18 |
Alyssa Ross | cool :) | 13:56:17 |
Alyssa Ross | hopefully I'll have a start by tomorrow | 13:56:38 |
j-k | In reply to @j-k:matrix.org 3 failed tests on bison I'm just assuming this is an issue introduced by binfmt so I'm back to x86_64-linux cross compiling. currently on the kernel | 14:18:06 |
j-k | nixos-sd-image-22.05pre-git-riscv64-linux-visionfive.img.zst π | 14:36:14 |
j-k | the sd image from the visionfive PR just has sda1 and sda2, I thought it needed stuff in sda3 to play nice with the really weird boot config? Is there something else I need to do to the board first? | 14:45:20 |
j-k |
We have to use custom boot firmware since we do not support
StarFive's Fedora MMC partition layout. Thus, we include this in
the image's firmware partition so the user can flash the custom firmware.
anything I need to do here or will it be done automatically?
| 14:46:07 |
j-k | *
We have to use custom boot firmware since we do not support StarFive's Fedora MMC partition layout. Thus, we include this in the image's firmware partition so the user can flash the custom firmware.
anything I need to do here or will it be done automatically?
| 14:46:18 |
Rick (Mindavi) | In reply to @j-k:matrix.org I'm just assuming this is an issue introduced by binfmt so I'm back to x86_64-linux cross compiling. currently on the kernel Sounds like some good tests :) | 14:52:03 |
j-k | In reply to @rick:matrix.ciphernetics.nl Sounds like some good tests :) I had a look into gnu autotest but I couldn't see an easy way to get some more useful debug logs :(
here's the shortlist of the failing tests:
2: Invalid number of arguments FAILED (input.at:29)
64: Deprecated directives FAILED (input.at:3031)
314: Invalid uses of %empty FAILED (actions.at:192)
it mentions some stuff about log outputs but I didn't go too deep on it
| 14:55:54 |
| 26 May 2022 |
j-k | waiting on a new USB/Serial adapter since I can't find it anywhere π | 16:26:52 |
j-k | nix on fedora will do for now :D
[riscv@fedora-starfive nixtest]$ nix flake show --extra-experimental-features "nix-command flakes"
[28.5 MiB DL]
warning: creating lock file '/home/riscv/nixtest/flake.lock'
path:/home/riscv/nixtest?lastModified=1653588931&narHash=sha256-f42UZVlY8XbnjxqF55IKgebs%2fYWtcskSH9zH3J2NlW0=
ββββdefaultPackage
β ββββx86_64-linux: package 'hello-2.12'
ββββpackages
ββββx86_64-linux
ββββhello: package 'hello-2.12'
[riscv@fedora-starfive nixtest]$
[riscv@fedora-starfive nixtest]$ uname -a
Linux fedora-starfive 5.15.10+ #1 SMP Fri Dec 24 14:24:27 CST 2021 riscv64 riscv64 riscv64 GNU/Linux
[riscv@fedora-starfive nixtest]$ systemctl status nix-daemon
β nix-daemon.service - Nix Daemon
Loaded: loaded (/nix/store/ykfmk9wvh2v737njahn0m3g19vbxl25w-nix-2.8.1-riscv64-unknown-linux-g>
Active: active (running) since Fri 2022-05-27 02:12:18 CST; 4min 57s ago
TriggeredBy: β nix-daemon.socket
Docs: man:nix-daemon
https://nixos.org/manual
Main PID: 2532 (nix-daemon)
Tasks: 3 (limit: 8532)
Memory: 387.8M
CPU: 33.566s
CGroup: /system.slice/nix-daemon.service
ββ2532 nix-daemon --daemon
May 27 02:12:18 fedora-starfive systemd[1]: Started Nix Daemon.
May 27 02:14:07 fedora-starfive nix-daemon[2532]: accepted connection from pid 2583, user riscv
May 27 02:14:18 fedora-starfive nix-daemon[2532]: accepted connection from pid 2602, user riscv
[riscv@fedora-starfive nixtest]$
| 18:17:30 |
j-k | to get the tarball I just added riscv as a cross target and I needed a newer copy of boost
diff --git a/flake.nix b/flake.nix
index c464b8f7c..a32ab2a68 100644
--- a/flake.nix
+++ b/flake.nix
@@ -21,7 +21,7 @@
linuxSystems = linux64BitSystems ++ [ "i686-linux" ];
systems = linuxSystems ++ [ "x86_64-darwin" "aarch64-darwin" ];
- crossSystems = [ "armv6l-linux" "armv7l-linux" ];
+ crossSystems = [ "armv6l-linux" "armv7l-linux" "riscv64-linux" ];
stdenvs = [ "gccStdenv" "clangStdenv" "clang11Stdenv" "stdenv" ];
@@ -83,7 +83,7 @@
configureFlags =
lib.optionals stdenv.isLinux [
- "--with-boost=${boost}/lib"
+ "--with-boost=${boost173}/lib"
"--with-sandbox-shell=${sh}/bin/busybox"
"LDFLAGS=-fuse-ld=gold"
];
@@ -111,7 +111,7 @@
bzip2 xz brotli editline
openssl sqlite
libarchive
- boost
+ boost173
lowdown-nix
gtest
]
@@ -302,14 +302,14 @@
propagatedBuildInputs = propagatedDeps;
- disallowedReferences = [ boost ];
+ disallowedReferences = [ boost173 ];
preConfigure =
''
# Copy libboost_context so we don't get all of Boost in our closure.
# https://github.com/NixOS/nixpkgs/issues/45462
mkdir -p $out/lib
- cp -pd ${boost}/lib/{libboost_context*,libboost_thread*,libboost_system*} $out/lib
+ cp -pd ${boost173}/lib/{libboost_context*,libboost_thread*,libboost_system*} $out/lib
rm -f $out/lib/*.a
${lib.optionalString currentStdenv.isLinux ''
chmod u+w $out/lib/*.so.*
@@ -320,7 +320,7 @@
chmod u+w $LIB
install_name_tool -id $LIB $LIB
done
- install_name_tool -change ${boost}/lib/libboost_system.dylib $out/lib/libboost_system.dylib $out/lib/libboost_thread.dylib
+ install_name_tool -change ${boost173}/lib/libboost_system.dylib $out/lib/libboost_system.dylib $out/lib/libboost_thread.dylib
''}
'';
@@ -340,7 +340,7 @@
echo "doc manual $doc/share/doc/nix/manual" >> $doc/nix-support/hydra-build-products
${lib.optionalString currentStdenv.isDarwin ''
install_name_tool \
- -change ${boost}/lib/libboost_context.dylib \
+ -change ${boost173}/lib/libboost_context.dylib \
$out/lib/libboost_context.dylib \
$out/lib/libnixutil.dylib
''}
nix build .#hydraJobs.binaryTarballCross.x86_64-linux.riscv64-linux
| 18:18:17 |
| 28 May 2022 |
Yuka (she/her) | maybe a dumb question, did you use thermal paste for the heatsink? | 15:19:52 |
| 29 May 2022 |
| vt52 joined the room. | 07:26:43 |
j-k | I did because I had some but I'm guessing just putting it on as-is would cool it enough (not that I've done any testing)
worst case you could probably pop it back off by squeezing the teeth at the bottom and add thermal paste when you need it/when it arrives if you order some | 09:49:10 |
| 30 May 2022 |
matthewcroughan - nix.how | j-k: I haven't even taken mine out of the box yet! :D | 18:49:26 |
| Astro joined the room. | 20:44:23 |
Astro | mine arrived today and a few fellow hackers immediately got interested when I unpacked it | 20:45:24 |
| Magic_RB joined the room. | 22:09:38 |
| 31 May 2022 |
| fufexan joined the room. | 10:20:46 |
fufexan | my board came today π | 10:21:16 |
fufexan | sadly can't test it as I don't have a HDMI monitor lying around, nor HDMI->VGA adapter. also no USB-C multiplexer (if it can even output over usb-c).
I'll look into it more when I get hold of one of those things, or after my exam session ends (late June) | 10:22:37 |
j-k | you can use ssh
https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide#using-ssh-over-ethernet
or usb to serial
https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide#using-a-usb-to-serial-converter
for a terminal session | 11:00:59 |
matthewcroughan - nix.how | In reply to @astro:envs.net mine arrived today and a few fellow hackers immediately got interested when I unpacked it hehehe | 19:54:10 |
matthewcroughan - nix.how | nice | 19:54:13 |