Did you update haiku sources, haikuports, haikuports.cross, buildtools, and made a clean build? The fix involved changes in all of these repos, and has been checked by several developers.
@PulkoMandy, Yes, I have updated everything as suggested in a previous message. I had reproduced the issues in two different machines. Today I reproduced the steps described in #14842 in a third machine and the build broke with a “cannot find -licu-le-hb” error while processing target ‘…/lib/libiculx.so.57.1’. This was the error that I hacked with the symbolic link.
I am testing in a Ubuntu 18.04.02 LTS environment and following the steps described in the issue. Since the CI builds are still broken I would be interested to know the environments and steps of successful builds.
The nightly builds are not bootstrap builds, so indeed these are still broken. See the “bootstrap build” section of https://github.com/haiku/haiku/blob/master/ReadMe.Compiling.md
For sparc I did it on my Debian system, but it may be easier to use kallisti5’s preconfigured docker images from here: https://git.haiku-os.org/haiku/tree/3rdparty/docker/bootstrap . In either case the instructions there may contain additional relevant info.
1 Like
Yes, the docker images make bootstrapping much less error-prone; probably a number of your ICU issues do not exist in them (at least kallisti5 successfully bootstrapped on them.)
@pemdp, you don’t need to do a bootstrap anymore though, @kallisti5 uploaded new packages to the ARM repository, so “normal” builds can now be done.
Yes, binutils still throws some R_ARM_REL32, which is now tracked in this ticket. You can use LLD to work around them for now as noted there.
1 Like
Partial Vulkan support on Raspi 1-3. Just saying…