* Peter Johansson (rossolis8240@telia.com) wrote:
Hello!
Hello Peter!
In the last few days I have completed a crux-3.3 port on aarch64 (Raspberry Pi 3) Built all packages on it, core, xorg, gcc-7.1.0, binutils-2.28
How did you do that? From cross compilation or deploying the generic aarch63 image?
Got X11 to work yesterday with fbturbo. Been very stable all the time.
Added this to the Pkgfile to be able to make some packages (aarch64 unknown)
sed 's/abacus)/aarch64)/g' -i config.sub sed 's/abacus-unknown/aarch64-linux/g' -i config.sub
./configure --prefix=/usr --build=aarch64-linux-gnu
Thank you very much for the information provided. I've faced the build arch problem and some specific ports related to aarch64 too. We have ready a generic release for aarch64 [1] and another optimized one for the pine64 [2]. In both cases we try to keep near CRUX and specally with everything related to the toolchain. Currently we provide gcc 6.3.0 and binutils 2.27 (as CRUX and CRUX-ARM 32b). We don't plan to move far from CRUX in any port version, only for exceptions when we need to create a port overlay for specific device needs. Actually we don't have an rpi3 to provide an optimized release nor test the generic one on it. Good to know that someone else got CRUX-ARM working on this amazing device. The xorg fbturbo driver should work just fine, but without providing acceleration. I think, at least, it could be great to make a port for /opt/VC and firmware (I had something done for the raspberrypi 1 for video playing if I remember right). [1] http://resources.crux-arm.nu/files/devel-test/3.3/crux-arm-rootfs-3.3-64b-RC... [2] http://resources.crux-arm.nu/files/devel-test/3.3/crux-arm-rootfs-3.3-64b-pi...
Regards Peter Johansson
Regards, --- Victor Martinez Learning bit by bit | http://vjml.es