[haiku-development] Re: porting to ARM is a bloody thing
- From: "Lizbeth Mutterhunt, PhD" <lizbethmutterhunt@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 01 Feb 2021 13:03:48 +0100
Op Montag, 1. Februar 2021 12:48:29 CET schreef Fredrik Holmqvist:
Den sön 31 jan. 2021 kl 14:07 skrev Lizbeth Mutterhunt, PhD <
lizbethmutterhunt@xxxxxxxxx>:
Op Sonntag, 31. Jänner 2021 14:56:26 CET schreef Adrien Destugues:
Everything clear! gonna checkout haiku and buildtools and afterwards we'll
see
if it takes really 20 hours for just ./configuring. It's my first
cross-built,
so thx for the fast anwer!
Your build problems are probably due to the fact that FreeBSD uses LLVM,
not GCC
to build tools. I don't think anyone has had the time to make sure
everything works with LLVM.
Yup! it's llvm 11-devel here; this should do but the gcc3 commands remain the
same. I tried to --use-clang but I get "[ invalid command" before entering the
checking prozess. Also the --continue-flag doesn't work here but being on the
latest nightly built with updates in VM and on freeBSD it just refuses with
"no knewn flag --continnue".
When it comes to 32 bit ARM, we were working on the EFI part, but decided
to move
over to ARM64. UEFI on ARM does not allow floating point ops and some of
our build
packages were built for hardfloat. It is much easier to use ARM64 as it
allows floating
point even in UEFI. That being said, we still need to setup a lot of UEFI
bootloader for
ARM64.
forget ARM32, it's dead anyhow. ARM64, armhf is a good way to make the
turnover to the Rasperry Pi 4, seeing problems with the UEFI bootloader as it
is just a problem on EFI-boards amd64 to boot (get gooing but with a trick!)
half a year ago. Raspi4 has on the fat32-boot-partition a lottta .bcm files
and the .efi for booting. A good way to start is with two SD-cards, one with
the boot files and afterwards leading to the system on the second SD. this is
what BSD does at the moment.
This is something I hope to continue on, so joining #haiku on FreeNode on
IRC is a
good way to communicate. See my nick below.
/Fredrik Holmqvist, TQH
Thx Fredrik, but I'm afraid my programming knowledge is too bad for joining
such a IRC. I'll try in a few months again, maybe my bug is being corrected.
It's amazing how BeOS could survive but still missing some important data from
the commercial version in the 2000s, I think. We have a libreoffice, gimp, a
*good* design (maybe you find someone for additionalo artwork), a gcc-compiler
and here on this old notebook it made 1920x1280 out of the box! This is what
linux just can dream of (normally 1367x1024). There's a blue line circling on
the top of the screen but this is normal for this high resolution and a Intel
Second Generation Graphic card.
Yours,
Lizbeth
Other related posts:
