Hi Victor, I'm basically done with Crux Arm64b on Odroid C2. Overall, the Odroid C2 builds packages at circa 2.75 faster than reported times for other arm native builds (I'm not a fan of benchmarks, so not a firm statement against a specific alternative). For opt/xpdf, I changed a dependency from qt4 to qt5, the former being a bit outdated. The build opt/qt5 required a change from -reduce-relocations to -no-reduce-relocations. The build opt/ghostscript required a setting -DPNG_ARM_NEON_OPT=0 in CPPFLAGS because the arm neon optimisation source code requires an assembler source file that is not compliant to arm64 (the error message was less instructional than my root cause explanation). (I wrongly reported that ghostscript has been build.) I forgot to send you my odroidc2-arm64 port collection, which is an adaptation of pine64-arm port collection. Since my project goals are more towards removing packages, protocol support, and other software functions that are not necessary for some specific security-intensive applications, I am not inclined to keep up to date with package revisions. This is the meaning of "I'm basically done." Still, I might make a revision to my document for a section on building Crux packages, but it's not too high on my list of priorities. I wish to thank you and the Crux Arm team for this marvelous Linux distribution preparation methodology. Regards, - Thierry