after extracting so much useful information from this community I finally decided to join this one as well.
I have a specific question about the procedure to upgrade glibc. Yes, I know this is 'risky' and probably a bad idea, but it should be possible right? There's another question here: libc 2.29 on buster but it doesn't seem to have a reliable answer. My question isn't specific to 2.29; for example I'm trying to install 2.32.
glibc is compiled by my cross-compile toolchain (crosstool-ng) using the armv6-unknown-linux-gnueabihf template. Due to a bug in the 2.28 compilation of glibc there that I cannot seem to solve (see: github), the other option I'm left with is upgrading the glibc version on the target.
I tried replacing the libc.so in the rootfs by just mounting the SD card to my linux host machine (so no program would be using libc) but then mayhem occurs. The pi seems to boot just fine and responds to pings, but ssh'ing for instance becomes impossible.
I'm hoping for someone with a little more experience on the matter that hopefully points out the obvious thing I'm missing here.