Hello everybody,
I re up this subject :)
I m currently trying to cross compile haiku for rpi or rpi2 (I have the
both to try),
Is this page up to date ?
https://www.haiku-os.org/guides/building/compiling-arm
because have the platform switch from raspberry_pi to rpi and rpi2, and
when I try to follow the procedure I got this error message :
$> ../../buildtools/jam/bin.linuxx86/jam -q -sHAIKU_BOOT_PLATFORM=rpi2
haiku-floppyboot.tgz
warning: Invalid jamfile cache: Failed to read file info.
Starting build of type regular ...
Giflib support not available on arm
... sames ...
expat support not available on arm
AddHaikuImagePackages: package bash not available!
... sames ...
AddHaikuImagePackages: package zip not available!
/home/oktail/Workspace/haiku/*haiku/src/bin/makebootable/platform/rpi2/Jamfile:
No such file or directory*
/home/oktail/Workspace/haiku/haiku/src/system/boot/platform/rpi2/Jamfile:
No such file or directory
/home/oktail/Workspace/haiku/haiku/src/system/kernel/platform/rpi2/Jamfile:
No such file or directory
Skipping setjmp_test2.S test on non-x86
/home/oktail/Workspace/haiku/haiku/src/tools/makebootable/platform/rpi2/Jamfile:
No such file or directory
...patience...
don't know how to make kernel_platform_rpi2.o
...found 9617 target(s)...
...updating 1014 target(s)...
...can't find 1 target(s)...
...can't make 85 target(s)...
InitScript1
/home/oktail/Workspace/haiku/haiku/generated.armpi/haiku-floppyboot-init-vars
Archive
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/libroot_build_function_remapper.a
ar: le modificateur « u » est ignoré puisque « D » est le défaut (consultez
« U »)
ar: création de
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/libroot_build_function_remapper.a
Ranlib
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/libroot_build_function_remapper.a
Link
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/lib/libroot_build.so
/usr/bin/ld: *ne peut trouver -lsupc++*
collect2: erreur: ld a retourné 1 code d'état d'exécution
export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/lib
; /home/oktail/Workspace/haiku/haiku/build/scripts/rm_attrs
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/tools/rm_attrs
-f
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/lib/libroot_build.so"
cc -Xlinker --no-as-needed -lm -shared -Xlinker -soname="libroot_build.so"
-o
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/lib/libroot_build.so"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/atomic.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/byteorder.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/errors.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/find_directory.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/fs.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/fs_attr.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/fs_descriptors.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/misc.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/sem.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/thread.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/driver_settings.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strlcpy.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strlcat.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strnlen.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/KMessage.o"
\
-lsupc++ -lstdc++ \
...failed Link
/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/lib/libroot_build.so
...
BUILD FAILURE:
...failed updating 1 target(s)...
...skipped 4 target(s)...
...updated 2 target(s)...
If somebody have more up to date informations about rasp or ARM support I m
interested, I have time to spent for support and devices available.
Thanks
Regards
2015-02-13 20:56 GMT+01:00 Travis Geiselbrecht <geist@xxxxxxxxxx>:
Annoyingly, I think the USB is one of the harder parts of the Broadcomm
cpus on the RPis. It's a nonstandard, undocumented USB OTG host controller
that both the usb ports and the ethernet MAC/PHY sit on. There's a linux
driver for it, of course, so it may just be a hard slog to figure it out
from a driver. The rest of the CPU is pretty well documented at this point,
including the graphics side of things.
I got my RPi 2 yesterday as well, and cpu wise it's miles ahead of the old
arm11. A cortex-a7 generally runs just about as fast as cortex-a9, and
there are 4 of them. I'm going to use it at least as a target to hack some
of my os code on it as a good quad core arm SMP test. It would probably be
a decent haiku kernel bringup target.
Travis
