Hi Victor, first of all thank you very much for the great job that you and all staff are doing. if it could be of any interest, I can test it on raspberry pi 1b, b+, PI2 and PI3, and also on some olinuxino arm with A10 and A20 soc. 2017-02-24 22:05 GMT+00:00 Víctor Martínez <pitillo@crux-arm.nu>:
El 24/02/17 a las 13:27, Guido Caliandro escribió:
Hi all,
Hey Guido,
Is there any news about that? ;-)
we are currently working on the new release.
Current status:
- toolchain updated to 3.3: https://crux-arm.nu/gitweb?p=t oolchain.git;a=commit;h=6bb79eca2ee00803534ad224cdebb4145f7891a0
- crossrootfs built and deployed on the OdroidXU4 to build the generic rootfs: http://resources.crux-arm.nu/files/devel-test/3.3/crossrootf s-3.3-RC2.tar.xz.md5
- generic rootfs (RC2) ready for testing in any ARM device: http://resources.crux-arm.nu/files/devel-test/3.3/crux-arm-r ootfs-3.3-RC2.tar.xz
- initrd updated: https://crux-arm.nu/gitweb?p=i nitrd.git;a=shortlog;h=refs/heads/3.3
- kernel/vexpress: work in progress because I've found some problems since 3.2 release: https://crux-arm.nu/gitweb?p=kernel/vexpress.git;a=summary
Our process is based on CRUX, then, when CRUX is released, we use a jail with CRUX core ports to build our crosstools (toolchain) and the crossrootfs. When it's ready, we deploy the crossrootfs to the powerfull device, in this case, the OdroidXU4, to build the generic release in two stages (full build + full rebuild). When it's tested and fixed any problem found, we release CRUX-ARM 3.3. After this release, we start building optimization for all officially supported devices (in the same way, two stages).
This is a short summary of this documentation web page: https://crux-arm.nu/Documentation/HowDoWeWork
thank you bye
Guido
Regards,
-- Victor Martinez Learning bit by bit | http://vjml.es