12741 2018-05-10 05:16:01 +0000 distcc: upgrade to 3.3 2018-06-01 02:08:56 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.5 x86 Multiple RESOLVED FIXED Medium+ normal 2.6 M1 1 ross.burton hongxu.jia meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 80538 0 ross.burton 2018-05-10 05:16:01 +0000 We're currently shipping what was once distcc 3.2 but upstream changed their repository and the SHA disappeared so Sumo ships using Armin's personal clone of an old distcc repository. This is bad. We should upgrade to 3.3 asap. There was a previous attempt but it failed to pass selftest. 80682 1 hongxu.jia 2018-06-01 02:08:56 +0000 Merged to oe-core commit dea59aab5d785d4f892cc26a8ea06eb4a6c554b3 Author: Hongxu Jia <hongxu.jia@windriver.com> Date: Sat May 12 00:15:20 2018 +0800 distcc: update to 3.3 * update to version 3.3 * Remove 0001-zeroconf-Include-fcntl.h.patch since it's included in v3.3 * Add update-distcc-symlinks into FILES. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> * Correct upstream SRC_URI and SRCREV to v3.3 * Correct default to fix starting distccd service failed It caused by upstream commit: https://github.com/distcc/distcc/commit/920e8b922addea8c54e68cc29c1416753f532f78 ... commit 920e8b922addea8c54e68cc29c1416753f532f78 Author: Shawn Landden <slandden@gmail.com> Date: Mon Feb 26 11:29:14 2018 -0800 daemon: warn when masquerade is not setup ... Add option --make-me-a-botnet to disable the warning. * Use localhost to replace 192.168.7.0/24 which is inappropriate for runqemu slirp. [YOCTO #12741]