Michael Tokarev <m...@tls.msk.ru> writes:
> Control: reassign -1 src:qemu > Control: tag -1 + moreinfo > > 05.02.2019 22:12, Alex Bennée wrote: >> Package: qemu-system-common >> Version: 1:3.1+dfsg-2+b1 >> Severity: normal >> >> Dear Maintainer, >> >> This is a problem when running: >> >> apt build-dep qemu >> >> On a arm64 host. I also ran into other failures while trying: >> >> apt build-dep -a arm64 qemu >> >> On a multiarch setup. The root reason is that the s390 cross compiler >> isn't packaged for all of debian's release architectures. > > Hm. So how this should be done? Please note that gcc-s390x is only > listed in Build-Depends-Indep, not in Build-Depends, and the indep > target is really only buildable on x86 exactly _because_ > cross-compilers s/cross-compilers/some cross-compilers/ Most of the other architectures tend to at least have their 32 bit cousins as well as x86 cross compilers available. However x86 currently has the largest breadth of cross compiler support. > are not available on other architectures. Ideally I'd like to support more cross compilers on more host architectures. However my attempts at getting all target binutils on arm have stalled somewhat and I suspect it's too late for the buster release cycle. > What should the dependencies look like? I'm not sure - it does seem weird that we are treating what is in effect an s390x architecture blob as architecture independent. I guess QEMU is good at generating weird exception cases. How did we ship s390x blobs on non-x86 release architectures before this change? > > Thanks, > > /mjt -- Alex Bennée