So, I was reading this page Using Jam | Haiku Project to correctly configure jam for my needs. But I am not understanding this section very well: Using Jam | Haiku Project (the sudo jam part) as to why the generated folder can only be accessed as root? Can somebody kindly explain that section in more detail? I am a bit afraid that I might do something stupid here and loose all my data.
It sais, basically: if you use sudo jam then those files will only be accessible to root.
What this means is that the build, and all subsequent commands will also run as the root user, and the files that will be created will have their user and group set as root.
Also if sais that jam rules, which like any build system, feature arbitrary code execution, is not a good idea to run as root as it may trash your system.
So basically, just donât use sudo to compile jam targets : )
Yeah I understood that first bit. But what actually made me confused was that I actually didnât ran jam as sudo as the building for x86_64 page says. But even after that, I got spammed with permission denied messages when I tried to recompile haiku after a small modification. The only clue that I have is that probably virt-manager might be somehow responsible for this because it requests su permissions before I created a vm using the freshly prepared image.
On which files? Check the permissions for those files and see what they have.
Having to run virt manager as root sounds wrong to me. Atleast with qemu (even with kvm) i never ran it as root on linux⌠maybe some files in /dev have wrong permissions?
I looked into it there is message telling me that âsystem policy prevents management of local virtualized systemsâ. Adding my user to the libvirt group will probably solve that problem but not sure about the permission issues. I will try to find some more details.
Usually device files required for stuff like this are owned by the group required. That could be libvirt, could be something else. Depends on your distro.
I recently updated to a custom build to test radeon_hd and now I am getting the expected speed. So, ig as you mentioned the issue is fixed in a recent nightly build. Thanks
Hello, is there a way to switch to a different mirror or manually download the packages (.hpkg) needed by haiku during a build? For some reason I get extremely slow download (like 10-20 KiB/s speeds sometimes from the haiku eu mirror. I am building from my main machine (debian) so the internet is fine.
Unfortunately we donât really have a mirror setup at the moment. The packages should only need to be downloaded once; on subsequent builds they will be cached in the generated/download
directory and not re-downloaded.
Oh I see. Not a big deal. I can just leave it running for a few hours.
I saw that Haiku will not be there in GSOC 2025. Canât say that I am not disappointed but on the positive side ig this gives me a opportunity to play around and contribute at my own pace
Also, I plan to add/maintain the packages for SDL3 and itâs satellite for haikudepot.