Ok, I’m assuming, if I don’t do a “git checkout” on the build tools, then the version I’m working with is the latest, correct? And, probably doesn’t work, to build Haiku (RISCV) hrev57197 properly, right? Thus, the version that directly precedes Haiku (RISCV) hrev57197 is btrev43203, which is dated 2023/6/20. And the very next btrev is the day AFTER (2023/8/5) the last successful build of Haiku (RISCV) hrev57197 (2023/8/4), so logically, it was being built with the prior revision of the build tools, because you can’t build older revisions of Haiku with newer tools you haven’t created yet.
David Karoly found a bug and fixed it, the fix was just merged. So you may be able to build and use the latest version now. That will be simpler than building older ones
You can also check the next nightly build and see if that works again.
Part of this adventure is the learning process. Doing something you didn’t know how to before. Figuring out how to fix something that was broken before. Learning new things, different things, is what life is all about. This is far from just getting to use Haiku on a different/new platform. Haiku is Haiku on EVERY platform. But, why do we choose one platform over another, to run Haiku? There must be a reason, or else we’re just “spinning teapots”, so to speak.
Update: Ok, now I’m getting mad. I’ve downloaded the buildtools. I checked out the btrev just prior to the day after the last working build of Haiku (RiscV). And now, the tools won’t build! So, how on earth did anyone create the Haiku (RiscV) hrev57197 image?
Haiku >= hrev57453+2
I haven’t rebuilt on the latest hrev57475, but review the build notes in the other thread where we covered a lot of the previous build issues.
~/haiku/generated.riscv64> jam -j2 -q @minimum-mmc
Starting build of type minimum …
Building Haiku Minimum Target
build-feature packages unavailable on riscv64: glu mesa fontconfig gutenprint webkit jasper qrencode_kdl tiff openexr libdvdread libdvdnav libraw libavif live555
AddHaikuImagePackages: package icu66 not available!
/boot/home/haiku/src/add-ons/kernel/bus_managers/isa/arch/riscv64/Jamfile: No such file or directory
/boot/home/haiku/src/add-ons/kernel/debugger/disasm/riscv64/Jamfile: No such file or directory
/boot/home/haiku/src/bin/debug/ltrace/arch/riscv64/Jamfile: No such file or directory
Asked for riscv target boot platform
Unknown path to handle adding to image
…patience…
…patience…
…patience…
…patience…
…patience…
…patience…
…patience…
…found 61016 target(s)…
…updating 8358 target(s)…
InitScript1 haiku.image-init-vars
C++ objects/haiku_host/x86_64/release/build/libbe/support/ZstdCompressionAlgorithm.o
InitScript1 objects/haiku/riscv64/packaging/packages_build/minimum/hpkg_-haiku_loader.hpkg/scripts/haiku.package-init-vars
…/src/kits/support/ZstdCompressionAlgorithm.cpp:17:12: fatal error: zstd.h: No such file or directory
17 | #include <zstd.h>
| ^~~~~~~~
compilation terminated.
I deleted both /haiku and /buildtools, then redownloaded everything and built the buildtools as-is. Ran jam -j2 @minimum-mmc (no -q) and got a lot further before it failed. Then ran jam -j2 -q @minimum-mmc and got only this far. Is this the first fault point or did I possibly mess things up by running jam without -q?
Thank you, X512! That did the trick! Had to remove -q in the jam command line, for it to complete successfully, but I am also happy to report that Haiku (RiscV) hrev57475 boots to the desktop in QEMU!
Now, next on my list is to figure out how to remove or add apps to the image. I’ve spent a while digging through the /haiku folder and the Jam files and such, but not seeing any direct connection. Nothing that says, “put these applications/applets/preferences in this platform image”. Or is there something I overlooked?
Aside from the default apps that come with the image you won’t be able to install anything there (I presume) because there is no buildmaster running builds for third party packages there.
You could setup haikuporter and build there yourself I think (think I saw @X512 doing something like that before).
This will show you the apps and packages usually included during the jam build process - but more info may be in the Haiku docs for riscv64. I think the packages are built during the jam process and/or prebuilt from X512’s repo.
Whoa… wait a second… you say your latest revisions have VisionFive 2 SD card boot support? As in, you can now boot Haiku off of an SD card on the VisionFive 2?!? This is the one thing I’ve been wanting/waiting for, to pull the trigger on buying a VisionFive 2!
Ok, can you detail the steps I need to go through, once I get a VisionFive 2, in order to get Haiku running on the VisionFive 2? I mean, I’ve read you gotta do this and that to get the latest firmware and all whatnot. So, I want to make sure I do everything EXACTLY in the right order.
I am also pleased to report, I’ve gotten QEMU running in Haiku now! I was using the Windows version before. However, after a few hours, I finally figured out how to get QEMU (I pronounce it “Chem-You” but maybe it could be pronounced “Keem-You”, but probably not “Queem-You”… unless you’re planning on pummeling someone, but you have an Elmer Fudd speech impediment… “You waskely wabbit… I’m gonna queem you!” ) running.
But it functions a bit different than the Windows version. Here is my command line for it:
As you’ll notice, I had to tell it the path to both the u-boot.bin file as well as the haiku-mmc.image file. I think this is because I was completely unable to copy the files to where I think they would normally go in the system directory (Windows 11 protests, only slightly, asking that I give it Admin privilage to copy files). I kept being told I couldn’t put files there, as it was a read-only directory, and I could not find a way to override that. So… whatever works!
Is there a complete guide somewhere about firmware updates (for the VisionFive 2) and what order to do things, or is it the “sitting up all night and searching the internet game” as usual ?[quote=“Luposian, post:33, topic:14369, full:true”]
Whoa… wait a second… you say your latest revisions have VisionFive 2 SD card boot support? As in, you can now boot Haiku off of an SD card on the VisionFive 2?!? This is the one thing I’ve been wanting/waiting for, to pull the trigger on buying a VisionFive 2!
Ok, can you detail the steps I need to go through, once I get a VisionFive 2, in order to get Haiku running on the VisionFive 2? I mean, I’ve read you gotta do this and that to get the latest firmware and all whatnot. So, I want to make sure I do everything EXACTLY in the right order.
[/quote]
) running.