Hi, Quoting Nick Leverton (2014-11-21 01:50:54) > TL;DR Dpkg does the useful thing, apt-get build-dep doesn't. > > I've just been getting a setup working for Debian cross-building. > At work I use OpenEmbedded which is a time consuming pain in > the neck. I hope to get to a work flow that can replace crappy > embedded vendor toolchains but for the moment I'm following Wookie's > recipe at https://wiki.debian.org/CrossToolchains which complements > his talk at Cambridge mini-debconf. To the extent that there is any > maintainer-supported user-level cross building support in Debian, this > seems to be it from my reading. > > However this bug is a significant blocker to that work process. > Several of the basic Priority Essential packages won't cross-build > with target != host because of the current bug. > > dpkg-checkbuilddeps already allows Arch:all Multi-Arch:none packages to > satisfy build-depends.
I don't think dpkg behaves different than apt here. Can you give the example? Maybe you are running into dpkg bug #710769? > I've built apt with the patch here and this allows "apt-get build-dep" to do > the useful thing also. Both the failures in the attached log go away with > this patch to apt. > > Please therefore can this patch be applied and released ? Treating Architecture:all packages implicitly as Multi-Arch:foreign would be wrong for many Architecture:all packages. Here two examples of Architecture:all packages that can NOT be marked Multi-Arch:foreign (without further work): - haskell-devscripts #769377 - dh-ocaml #769379 If apt would treat all Architecture:all packages as Multi-Arch:foreign then these two packages would have a wrong Multi-Arch annotation. This shows that marking packages as Multi-Arch:foreign must be done with care and not in an automated fashion. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
