troubles with rust / cargo / blake3 on Haiku

[ThomasWaldmann]

I am trying to add blake3 and it has some rust dependencies.

I could get all platforms working, except Haiku, see there:

• add blake3, blake2b is legacy #9643
• CI: https://github.com/borgbackup/borg/actions/runs/25876342869/job/76044614227?pr=9643

It seems it can't find cargo. Shouldn't that be in rust_bin package?

[ThomasWaldmann]

@mmuman @Begasus can you help, please?

[Begasus]

The command for cargo should be fine (from the CI failure):

~> cargo --version
cargo 1.94.1 (29ea6fb6a 2026-03-24)

Adding blake3 to the recipe here doesn't seem to have any effect, or failure not finding cargo (didn't add that to the recipe yet). How do I make sure it will be used during the build?

EDIT: does this use the blake3 rust crate? Because at this moment our blake3 package doesn't provide that (nor python module?).

[ThomasWaldmann]

I do not see the cargo version output in the CI log, but:

2026-05-14T18:00:11.5976260Z + cargo --version
2026-05-14T18:00:11.7288044Z ##[group]Tearing down VM
2026-05-14T18:00:11.7289214Z Syncing back files
2026-05-14T18:00:11.7307649Z [command]/usr/bin/rsync -auz user@cross_platform_actions_host:/boot/home/home/runner/work/ /home/runner/work
2026-05-14T18:00:12.0162571Z Terminating VM
2026-05-14T18:00:12.0179588Z [command]/usr/bin/sudo kill -s TERM 2358
2026-05-14T18:00:12.0260995Z kill: (2358): No such process
2026-05-14T18:00:12.0272298Z ##[endgroup]
2026-05-14T18:00:12.0295531Z ##[error]The process '/usr/bin/ssh' failed with exit code 4
2026-05-14T18:00:12.0603004Z ##[group]Run codecov/codecov-action@v6

So I am assuming cargo failed or is not there.

[ThomasWaldmann]

blake3 (package from pypi.org) is required by borgbackup's pyproject.toml, so it will be pulled and installed by that.

For the more popular platforms, that will fetch a binary wheel from pypi (no rust tools needed), but for the BSDs, omniOS and Haiku, there is no binary wheel, so it will build from source and need rust and build tools.

I only put that separate pip install command there to maybe get a more clear / better visible error output from a blake3-only install / build.

CI config: https://github.com/borgbackup/borg/pull/9643/changes#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03f

[Begasus]

Even with blake3, cargo and pip added into the recipe here, I still can't see any mention for blake3 during the build.

EDIT: when trying to launch a build from inside the recipe (outside also), I get a crash folowed by a rust error:

borgbackup_blake3.txt

[ThomasWaldmann]

build terminates as soon as there is a non-zero rc from a command. maturin is used by blake3, so i try to pip install that first. but cargo —version does not even work.

[Begasus]

I tried earlier (checking out blake3_py outside of haikuporter, so just in Terminal, that mentioned maturin in there, trying to install that with pip3 install --user maturin also failed. So this should be fixed first before being able to build blake3 for python.
Maybe our master python guru can shed a light here .... @OscarL ? ;)

[OscarL]

Far from being a guru of anything here but...

From the CI logs I can see linked here, there's not much I can say, "from the python side". As @ThomasWaldmann mentions, the line cargo --version doesn't seems to be working, ssh ends, and we don't even get to the pip install part.

Maybe the Haiku version on the CI VM is too old for the rust_bin/cargo package? Not sure how feasible is to update the image (will require an OS reboot to for changes in haiku*.hpkg packages to kick in).

Other than that.... I would try to get more detailed info about why cargo --version doesn't prints anything: maybe cat/tail/or copy the /var/log/syslog from the VM, it might contain crash/runtime_loader info or error messages.

---

@Begasus from your borgbackup_blake3.txt: both zerotrie and icu_collections fail to compile, I think from the same issue:

fatal runtime error: out of TLS keys, aborting.

That thing in particular might have been fixed in hrev59718.

---

Side note/light-nitpick: The name of the OS is just "Haiku" :-)

[Begasus]

Thanks @OscarL for stepping in, sometimes it's just handy to have a pair of eyes looking into this. 👍
On the cargo version, even with the "older" one that should just work?
On the TLS thing, I've seen it mentioned in the ML, would have to switch from beta5 to nightly to check that out.

[OscarL]

@ThomasWaldmann: a heads up... in the linked CI change, you're doing pkgman install -y rust_bin setuptools_rust. That won't do what you intend, as that setuptools_rust is just an empty base package, and not the one you probably want... pkgman install -y setuptools_rust_python310 (this is a quirk/bug/mis-feature from HaikuPorter).

[Begasus]

Update: switched to nighly to check: pip3 install --user blake3 works, building and packaging borgbackup with haikuporter also worked, added almost 1MiB to the package, so something must be added (although I still don't see any blake3 mention in the package files). :)

[ThomasWaldmann]

Glad to hear that it works on nightly, it's just that this won't help our CI, which is based on cross-platform-actions project and only offers that (meanwhile rather old) Haiku beta.

I was assuming that setuptools_rust pulls the setuptools_rust_python310 as a dependency. But I don't know whether it even matters, adding that was just a random attempt in trying to get things working.

I'll try to get more logs...

About blake3 being mentioned in "package files" (which package files?) - this is only a pull request yet and it is mentioned in pyproject.toml in that PR. master branch ("borg2") does not yet use blake3 and 1.4-maint branch won't get blake3.