New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distcc fails to build when calling clang or clang++ #368
Comments
it looks like i have same situation |
Any way i can help? |
While you did not include the distccd log necessary to know for sure, this is probably a duplicate of this debian bug: |
@shawnl - I attached a debug log to the first post in this I thought. Can I provide you with something else to help? Also, I am not using |
FWIW, following the instructions here (which were written for icecc) helps a lot with the Of note, pump mode still has a problem, because it interprets
though in retrospect, |
@henryptung - Thanks for sharing that link. I modified my flags, adding two mentioned in the link:
Now I am getting distcc distributing out to my two volunteer machines (THANK YOU)! Interestingly (perhaps to be expected?), the build log is full of notes and warnings. Normal?
|
@graysky2 I also got a bunch of warnings, going to guess normal. Sadly, the line I mentioned got changed before 83.x, so for now the distcc patch seems to be the only way to make pump mode work. |
I am going to close this issue since the problem isn't with distcc but with the way I was compiling chromium. @henryptung - Thank you again for pointing me to the solution. Now, it only takes 3 hours to build chromium whereas with distcc, it took 5-1/2 hours. |
@graysky2 Er, wouldn't close this bug. The listed strategies from the referenced page are workarounds - ways that happen to make the build avoid troublesome clang features that choke up distcc. However, there's no fundamental reason why distcc shouldn't support/handle those features (e.g. I think a later version of icecc fixes at least one of the two), and there's no guarantee that those workarounds will still work in future versions of chromium (which may no longer provide an opt-out for those flags). |
@shawnl - Any thoughts? |
@henryptung - Looks like chromium 87.0.x.y breaks distccd despite the work arounds:
UPDATE: I found this: https://www.cnblogs.com/bigben0123/p/12551318.html Adding these in addition to the two flags from your initial URL allowed distcc to work again to compile chromium. I should say that I also updated distcc to the latest git. For reference:
UPDATE2: this fails to build after 4000 steps in or so.
|
Remotely AND locally. There is nothing in GCC can take that argument but clang cannot. Chromium thinks it is building on gcc but you are using clang. This is not a distcc problem. |
I did test locally and the build completes without error. |
in addition to the upstream bug report, Arch ARM is building with the following flags which I am currently trying on x86_64. So far, I am seeing good distribution out to my distcc cluster.
EDIT: I commented out the 'use_allocator=" since I have been removing these one-by-one and checking to see if the build progresses for 10-12 min. It seems that particular one is not required. |
Distcc 3.3.3 cannot build using clang or clang++ on Arch Linux. Trying to build chromium for example, gives output like this on the client:
Verbose distcc.log on the volunteer. Any thoughts are welcome.
The text was updated successfully, but these errors were encountered: