build-depends snarfing should also "cross" the arch-specific build-depends
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
armel-cross-toolchain-base (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
armel-cross-
g++-multilib [amd64 i386 mips mipsel powerpc ppc64 s390 sparc kfreebsd-amd64]
But g++-multilib is a build-dependency used when building *native* toolchains on these architectures. When building an armel cross-compiler, this is superfluous.
The debian/rules magic should parse these build-dependencies, stripping out all architecture qualifiers, and discarding any arch-specific build-dependencies that don't apply to the target architecture (armel). See Section 7.1 of debian-policy 3.9.0 or later for a full explanation of the architecture matching rules that apply.
Related branches
Changed in armel-cross-toolchain-base (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
importance: | Wishlist → Low |
assignee: | nobody → Marcin Juszkiewicz (hrw) |
Changed in armel-cross-toolchain-base (Ubuntu): | |
status: | Triaged → Fix Committed |
started test build without g++-multilib dependency - will see