On Sat, 15 Dec 2018 17:22:56 +0100 Helmut Grohne wrote: > > squid fails to cross build from source for a number of reasons. The > immediate failure is with the g++ build dependency as that conflicts > with the build architecture g++. For properly expressing the dependency, > we'd need "toolchain dependency translation", which isn't a thing yet. > However, the relevant dependencies are always satisfied since stretch. > Therefore, we can simply drop them.
These GCC|Clang versioned depends are to fix backport and custom build FTBFS. We still have quite a number of people using self-compiled Squid in order to gain the TLS interception features from OpenSSL. Those tend to be squid-4 packages on older Debian and Ubuntu machinery where GCC version still matters. So while I would love to have fully working cross-build support the trade-off with lost users is not really worth it until Debian and derivative LTS versions move on from the outdated GCC-4.x compilers. I am not sure I understand what you mean by a conflict with the build architecture g++. - the build arch g++/gcc are used during Squid build and needs to meet that version criteria for correct operation. - the cross-compiler also needs to meet it, but we don't have a way to indicate that dependency. If the cross-compiler is old enough to conflict or break with a required BUILDCXX version it would seem the cross-compiler is not going to work properly anyway. What am I missing here? The other changes I have merged into our git branch for the next package upload. AYJ
