Well, in my last post I discussed getting OpenADK to build a dev environment on the TS-7670. I had gotten Gentoo’s Portage installed, and started building packages.
The original plan was to build everything into /tmp/seed, but that requires that all the dependencies are present in the chroot. They aren’t. In the end, I decided to go the ill-advised route of compiling Gentoo over the top of OpenADK.
This is an ugly way to do things, but it so far is bearing fruit. Initially there were some hiccups, and I had to restore some binaries from my OpenADK build tree. When Gentoo installed python-exec; that broke Portage and I found I had to unpack a Python 2.7 binary I had built earlier then use that to re-install Portage. I could then continue.
Right now, it’s grinding away at gcc; which was my nemesis from the beginning. This time though, it successfully built xgcc and xg++; which means it has compiled itself using the OpenADK-supplied gcc; and now is building itself using its self-built binaries. I think it does two or three passes at this.
If it gets through this, there’s about 65 packages to go after that. Mostly small ones. I should be able to do a ROOT=/tmp/seed emerge -ek @system then tar up /tmp/seed and emerge catalyst. I have some wrapper scripts around Catalyst that I developed back when I was responsible for doing the MIPS stages. These have been tweaked to do musl builds, and were used to produce these x86 stages. The same will work for ARMv5.
It might be another week of grinding away, but we should get there. 🙂