On Thu, 1 Nov 2012 01:00:14 -0600 Ryan Hill <[email protected]> wrote:
> This has nothing to do with dependencies not getting rebuilt when the library > does. It's about switching to an earlier compiler version and having > every single package depending on that library fail to build due to something > that is non-obvious and hard to track down. You don't know that you have to > rebuild the library because you don't know which package that damned flag came > from. I've had someone try to make the argument that we don't really "support" users mixing packages built by different compiler versions. It is true that doing so can sometimes lead to problems with ABI compatibility, unsupported flags, and so forth, as well as more subtle issues due to compiler bugs, etc. Sometimes there is nothing we can reasonably do about this and we have to live with it. Other times there are solutions, such as making sure that ABI-changing options don't get propagated down to other packages through foo-config/pkg-config scripts, or ensuring packages honor the users compiler flags (see for a topical example bug #202059), and we should and do fix these things when we encounter them. What we don't do is make the situation worse by actively introducing these things into the tree, knowing full well the problems they can cause, and hide behind the excuse that it's unsupported. -- gcc-porting toolchain, wxwidgets we were never more here, expanse getting broader @ gentoo.org but bigger boats been done by less water
signature.asc
Description: PGP signature
