October 10 2015 4:07 AM, "Adrien Destugues" <pulkomandy@xxxxxxxxx> wrote:
On Sat, Oct 10, 2015 at 10:28:15AM +0200, LECOQ Vincent wrote:
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
It's as up to date as we have. I'm not sure what the exact status of the
Pi port is.
You need to configure the build with the proper target board set:
mkdir generated.armpi; cd generated.armpi
../configure --build-cross-tools arm ../../buildtools --target-board
raspberry_pi
Then try to build an MMC image:
jam -q @minimum-mmc
As far as I can tell, the switch to rpi1/rpi2 is not complete, as there
are still a lot of folders named "raspberrypi_arm" (where your build
attempt is looking at "rpi2").
So it seems the first step is cleaning up the name of the target board
and sticking with one choice. The @minimum-mmc target is the one to use
for the ARM ports at this early stage, so I would focus on getting that
one running. It should eventually build an MMC/SD image with the
required boot loader and kernel (no userland yet).
Help is welcome in getting the buildsystem running for the Pi targets,
and updating the documentation accordingly.
/usr/bin/ld: *ne peut trouver -lsupc++*
collect2: erreur: ld a retourné 1 code d'état d'exécution
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/atomi
.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/byteo
der.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/error
.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/find_
irectory.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_at
r.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/fs_de
criptors.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/misc.
"
"/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/threa
.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/drive
_settings.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strlc
y.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strlc
t.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/strnl
n.o"
"/home/oktail/Workspace/haiku/haiku/generated.armpi/objects/linux/x86_64/release/build/libroot/KMess
ge.o"
\
-lsupc++ -lstdc++ \
However this is an error while trying to build tools for the host Linux
system, I'm not sure it is related to building for ARM. Does a regular
build for the x86-gcc4 (or x86_64) target works for you? You can try it
in a separate generated folder.
libsupc++ may not exist on Linux, so I don't think the build system
should be linking it in here.
