Some days ago, I found an interesting repository about android tools which can be built without GO compiler (check it here). If you're familiar with adb, fastboot, etc, you know what I'm talking about. It suits me because I have no GO compiler or won't bother to download one because I already have GCC. After firts successful build which result on dynamic linked binaries, I'm curious on building the static linked one. Here is how I did it !

Before we go deep into building stuffs, we need to prepare some stuffs.

• Make sure you have GCC / Clang !
• Satisfy the dependencies, check on the README !

Since I moved to source-based linux distro with musl (Dragora GNU/Linux & LFS Musl), I always wondering about how to run android platform tools on musl. Android platform tools seems built againts glibc so running it on musl is almost impossible. Not until I discovered about patchelf. Turns out, we can use patchelf to make android platform tools binary tool (adb, fastboot, etc) to run on musl, with a bit of trick of course.

After did some trials and errors I found a way to build gettext library + its libintl.so library on musl. I need the library so cosmic-files will work properly. Before I finally built gettext + libintl.so, everytime I build gettext I only get libgnuintl.so instead of libintl.so. Turns out, the solution is pretty simple. I just need to rename libintl.h header file from musl build and boom, gettext build will produce libintl.so instead of libgnuintl.so.

• Musl (obviously).
• gettext, I use 0.24 version.

• Musl based distro archive.
• Appimagetool.
• Text editor.

Honestly, I don't really know.

• Editor text, I use vim.
• Sshd init service file, It usually exist at /etc/rc.d/init.d/sshd.

We need some stuffs to be prepared, like :

• Musl-based linux distro as host. I used dragora GNU/Linux. We may use alpine as well.
• Compiler, I use gcc 14.
• LFS book, just ignore everything about the glibc, openssl and eudev part.
• Mussel to build cross compilers.
• Time and patient.