On 2017-08-28 19:16, John Paul Adrian Glaubitz wrote: > On 08/28/2017 06:30 PM, W. Martin Borgert wrote: > > But my experience is quiet good with this: > > > > ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- dpkg-buildpackage > > -rfakeroot -aarmel ... > > > > I don't remember what the ARCH variable is used for. > > Maybe it is not needed. > > You shouldn't be building packages like that if you want to guarantee that > they > will actually work in the target environment since your approach is not > building > in a clean environment. Also, this way you will have to install all build > dependencies > yourself.
This depends on the build process: In my case we build in a clean environment with all build dependencies pre-installed. Remember, this is not a generic Debian build process, but a specialised one for certain packages. > > Yes, we develop for squeeze in a squeeze chroot or VM, and for stretch > > in a stretch container. Multi-arch makes things easy on stretch, that > > were difficult on squeeze (dpkg-cross, apt-cross, ...). > > Or just create chroots for the architectures you need with qemu-debootstrap. > No > need to use any fancy containerization fuzz. All you ever needed was a chroot > and sbuild, no need for a bigger software stack written in Golang on top of > that. No Go/docker here, nor qemu, just systemd-nspawn :~)