On Jun 1, 2020, at 12:59 AM, Helmut Grohne <hel...@subdivi.de> wrote: > > Hi Stephen, > > On Sun, May 31, 2020 at 11:47:38PM -0500, Stephen Gelman wrote: >> I just published 4.1.0-3 which applies your changes. If you’d be willing to >> point me in the right direction as to an easy way to reproduce the failures >> you were seeing I’d be happy to dig into the luajit issues you are seeing. I >> don’t have any experience cross-building packages (and minimal experience >> cross-building in general) but I’m always happy to learn something new! > > Thank you. Cross building Debian packages is relatively simple these > days. If you are using sbuild, you pass --host=$SOMEARCH and if you are > using pbuilder, you pass --host-arch $SOMEARCH. No special setup needed. > Another easy way is waiting a few days and checking > http://crossqa.debian.net/src/wrk to have it built by qa. > > The luajit issue is none for the faint of heart unfortunately. The > luajit tool produces ELF objects containing the byte code when being > given the -b flag. Unfortunately, there doesn't seem to be a way to tell > luajit which architecture we need ELF objects for. So this issue needs > to be fixed on the luajit side first. It's not entirely clear whether > this can be fixed with reasonable effort, but having build logs that > show how this fails (such as wrk) makes it much easier to reason about > this on the luajit side. I suggest that you leave it as is unless you > look for a time sink. > > I also think that luajit is wrongly marked Multi-Arch: foreign for this > reason. > > Helmut
Helmut, Thad does sound pretty rough… I may let this one lie for a bit then, but this is very helpful info regardless! Thanks! Stephen
