Well goodness me, seems I spoke too soon. I found the that zlib was required (looking for "zlib.h"), so I built that first and that too wasn't all that cross-compile friendly. I saw "CHOST" is used, and was surprised that it didn't seem to need anything to link against from the target sysroot, so that turned out better than I thought it would. I then used `configure` prefixed with the`CFLAGS="--sysroot=<pathToSysroot>"`, along with `HOST_CPU=<tuple>` for `make`, and it worked out fine. Before moving it to my device, I just nspawned/chrooted into it and `git --help` worked. So looks good and easy steps. Of course, it'll depend on whether or not a git function using zlib also passes (hoping zlib actually built fine without needing any outside linkage). I'd still suggest and prefer that git (and zlib) follows what others have settled on doing to be cross-compile-friendly. On Mon, Jul 8, 2024 at 11:52 AM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote: > > A few years ago, I had started adding cross-compilation support to the > project but never finished the task. I'm pretty sure I still have the > patches sitting around somewhere. I'll look for them, but I'm not sure > how much they will help. Aside from the obvious patch adding > `config.guess` and `config.sub`, I recall creating a patch to fool > `autoconf` into not demanding that the project also carry the bunch of > other scripts/tools `autoconf` normally wants (since we don't use > those tools in our build process). > > [*] https://lore.kernel.org/git/20171209094310.GA60808@flurp.local/
