Package: src:gcc-4.8 Severity: normal Hi. This is the cross-build-specific half of the patches originally posted in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738152 The first half (filled-in missing logic) is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740005 This set of patches sets up some cross-building-specific logic when building a cross-compiler with with_deps_on_target_arch_pkgs=yes The patches are very similar to those in the original set. The only difference is the set of languages for which a compiler is built. The changes in this set are: - Don't build a source package if we're building a cross compiler - Don't build libraries if we're building a cross compiler using the host's libraries (with_deps_on_target_arch_pkgs=yes) - Do not build a java or D cross-compiler. Do build the rest of the languages (C,C++,objC, objC++, go, fortran) The benefits this patch series provides: - Unneeded libraries aren't built, so the build completes faster - Currently the libraries that get build using with_deps_on_target_arch_pkgs=yes are different from those that are built natively. For instance libstdc++6 in the main debian archive is Multi-Arch:same, while the package we get with with_deps_on_target_arch_pkgs=yes has no Multi-arch tags. This is a potentially very confusing discrepancy, and not building the "wrong" package at all is good, I think. We can fix the tags, but it's unclear who would benefit. - There's an issue regarding an inconsistency in the naming of the x86 32-bit platform (debian calls it 'i386', gcc,binutils call it 'i486'). This results in build errors when trying to build cross-gcc-libraries for the i386 target. These patches don't build those libraries, so we don't see those issues. We could fix the underlying problem, but again, it's unclear this is useful to anybody. dima
gccpatches_2014_03_10.tar.gz
Description: Binary data
