On the failing host: FEATURES="-distcc" emerge mysql -> succeed FEATURES="distcc" emerge mysql -> fail On another host, with or without distcc, it works. None of my distcc hosts have the synch.h file, all have it from kernel source, but only for powerpcc arch, and all my hosts are x86. Reproducible: Always Steps to Reproduce: 1. impossible: on some hosts it works as-is, only this one need distcc off. 2. 3. Actual Results: the cmake log show clearly that cmake found synch.h, dunno where it found it, but it shouldn't found any. <Determining if files synch.h exist passed with the following output: Change Dir: /var/tmp/portage/dev-db/mysql-5.6.25/work/mysql-abi_x86_32.x86/CMakeFiles/CMakeTmp> Note also that mariadb share the same problem, find a synch.h file, try to use it, fail. I didn't test if mariadb was buildable when distcc is off. - the cmake log showing it found the synch.h where there's none from /var/tmp/portage/dev-db/mysql-5.6.25/work/mysql-abi_x86_32.x86/CMakeFiles - the build log where pthread.h refer to synch.h if the ifdef is set, as it is set by previous test, it try use it and fail. - failing host emerge --info when distcc is enable.
Created attachment 411498 [details] emerge --info
Created attachment 411500 [details] cmake log with synch.h test succeed
Created attachment 411504 [details] build log
Ah i figure it out the "my other host using distcc build it" mystery. The failing host is using pump, while the other is not (it doesn't need that much help). On the failing host, i'm now able to build it with FEATURES="-distcc-pump". Of course when i was using FEATURES="-distcc" it was also disabling pump allowing it to build. So someone should test: mariadb and mysql ebuild fail if distcc-pump is enable ; but works with distcc out of pump mode.
I'm having the same issue.
*** This bug has been marked as a duplicate of bug 645298 ***
the real solution to stop this mess, should be that an ebuild which use cmake should disable distcc-pump, that's what they are force to do to have the package built anyway.
