hi, look at save_temps variable or set DISTCC_FALLBACK=0 then error will be visible on stderr br Łukasz Tasz RTKW
czw., 26 sty 2023 o 04:02 Qu Wenruo via distcc <distcc@lists.samba.org> napisał(a): > > Hi, > > Recently I tried to re-setup my aarch64 distcc environment, as > previously it failed to do a proper remote compiling. > > But still, it failed to do a lot of compiling on the remove server. > > The setup looks like this: > > Client: Archlinux ARM, GCC 12.1.0, distcc 3.4 > Volunteer: Archlinux ARM, GCC 12.1.0, distcc 3.4 > > Volunteer should has the correct link setup. > (They all go with compilers like aarch64-unknown-linux-gnu-gcc) > > Kernel source: v6.2-rc kernel > > And the result is tons of error like this: > > distcc[15204] ERROR: compile drivers/pwm/sysfs.c on 172.16.0.220:3632/6 > failed > distcc[15204] (dcc_build_somewhere) Warning: remote compilation of > 'drivers/pwm/sysfs.c' failed, retrying locally > distcc[15204] Warning: failed to distribute drivers/pwm/sysfs.c to > 172.16.0.220:3632/6, running locally instead > distcc[14806] (dcc_please_send_email_after_investigation) Warning: > remote compilation of 'net/core/filter.c' failed, retried locally and > got a different result. > > The distccd only shows the summary of the failure on remote server: > (debug log level) > > distccd[1766] aarch64-unknown-linux-gnu-gcc arch/arm64/mm/fault.c on > localhost failed > distccd[1766] job complete > distccd[1766] (dcc_job_summary) client: 172.16.0.150:38012 COMPILE_ERROR > exit:1 sig:0 core:0 ret:0 time:2513ms aarch64-unknown-linux-gnu-gcc > arch/arm64/mm/fault.c > > Not mentioning what caused the compiling failure. > > Is there any way to properly debug the behavior? > > Thanks, > Qu > > __ > distcc mailing list http://distcc.samba.org/ > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/distcc >
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc