Summary: | sys-devel/distcc: distcc-pump breaks dev-python/pypy | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | WGH <wgh> |
Component: | [OLD] Unspecified | Assignee: | Michał Górny <mgorny> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | cluster, mgorny, python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/tmp/portage/dev-python/pypy-4.0.1/temp/build.log |
Description
WGH
2016-02-07 14:28:55 UTC
Created attachment 424860 [details]
/var/tmp/portage/dev-python/pypy-4.0.1/temp/build.log
Are you certain this is distcc's fault? Please try without FEATURES=distcc-pump, as it is known to be semi-broken. It certainly builds without distcc. And I have just launched a rebuild with distcc, but without distcc-pump. It's going to take a while, but it hasn't crashed yet, so maybe it will be built successfully after all. If it's indeed distcc-pump issue, I'm afraid I can't do anything to help. Long story short, distcc is pretty much a dead project that received one-time, half-ass revamp from an enterprise company that resulted in distcc-pump. Sadly, it is buggy and fails randomly (but works as far as enterprise is concerned!). It caused semi-random build failures with packages such as firefox or talloc for me. Interestingly, Firefox (at least the current ESR release, 38.6.0) builds fine with distcc-pump for me. I had failures for talloc, too. Additionally, qemu, ffmpeg, and probably something else. Could "blacklisting" FEATURES=distcc-pump for select packages be the "solution" for the problem? The blacklist entries, strictly speaking, should depend on both package and distcc version... not sure if that's possible at all. (In reply to WGH from comment #5) > Interestingly, Firefox (at least the current ESR release, 38.6.0) builds > fine with distcc-pump for me. > I had failures for talloc, too. Additionally, qemu, ffmpeg, and probably > something else. > > Could "blacklisting" FEATURES=distcc-pump for select packages be the > "solution" for the problem? The blacklist entries, strictly speaking, should > depend on both package and distcc version... not sure if that's possible at > all. We don't currently support anything like that, and I don't think it's worth the effort. Especially that we don't know what is exactly causing the issues -- it is also possible that distcc-pump is silently miscompiling some other packages, which are going to work incorrectly rather than fail to build. Therefore, I find it better to just disable it altogether and use plain distcc. I can now confirm that pypy builds with distcc, but without distcc-pump. Reassigning to distcc people. FEATURES=distcc-pump has been removed from portage. |