Krzysztof Halasa wrote: > Hans de Goede <j.w.r.degoede@xxxxxx> writes: > >> In my somewhat limited experience cross-compiling of software which is >> not designed for that from day one is a big pain, let alone >> cross-compiling an entire distro! > > It depends. I, for example, cross-compile all the stuff on PC, but > this PC (x86_64) is able to run simple ARM binaries (needed by > configure scripts etc) using binfmt+ssh to a real ARM machine. > Even without chroot is works fine, with chroot it would probably > be almost automatic. The scripts think I'm doing native builds. > > I assume one could use an emulator instead of ssh. I also went through that process with an ssh-based "execution proxy", but as I did more packages I found that later configure scripts generated by newer autotools try running less or no test programs on the target. For example some older configure scripts ran wanted to compile and run test apps to find out sizeof(int), newer ones work it out without having to run anything on the target. Therefore I now try to regenerate the configure script from configure.in using newer autotools as the first move when the dist configure script had problems for crosscompiling. -Andy -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
