El 15 abr. 2020 12:06, Guido Caliandro <guido.caliandro@gmail.com> escribió:

Hi all,

Hey Guido!

I would like to share with you my progresses on making CRUX-ARM working on my PI zero device.
After some positive results in cross-compiling sysvinit and merged it on CRUX-3.5 Generic, I tried to create my own CRUX-ARM system from devtools (https://crux-arm.nu/gitweb?p=devtools.git) as suggested me on IRC, but unfortunately my skills on these scripts are zero: I couldn't start any of them, and I found no tutorial to use them.

Since 3.5 we have avoided cross compilations. We build the releases nativelly on 32b and 64b devices.

What I've found are quick guides to create your own toolchain and how to cross-compile a single package.

The toolchain for cross building packages is ready, but not used. Then, crossrootfs isn't ready for 3.5.

Then I cross compiled and added to CLFS some of the package on crossrootfs, copied on the PI zero together with my pre compiled kernel, and it started!
Then I continued to cross-compile and copy on sd card other packages from crossrootfs, but unfortunately these packages are from CRUX-ARM 3.4 system, not 3.5, so I broken all my GLIBC and I started again from zero.

You need to update all crossrootfs ports and adapt them to the right versions, or you face those problems. You need to build and install on CLFS in the right order to keep a clean toolchain and dependencies. This is a hard task and with powerfull devices we don't need to waste time on that step now (needed for devices like the PI zero).

Now I have a working system (with limited packages), but I'm sure it's not the right way to do it (I had to add --host=$CTARGET to any package I wanted to make).
What I can't cross-compile is GCC, primary for let the PI zero working by itself

Please let me know your thoughts....

Cheers

Regards,