On 2023/1/26 17:29, Łukasz Tasz wrote:
hi, look at save_temps variable or set DISTCC_FALLBACK=0 then error will be visible on stderr
br
Łukasz Tasz
RTKW

Thanks a lot, got the offending stderr, it looks like preprocessing is causing something wrong?

```
In file included from ./include/linux/bitops.h:34,
                 from ./include/linux/thread_info.h:27,
                 from ./arch/arm64/include/asm/preempt.h:6,
                 from ./include/linux/preempt.h:78,
                 from ./include/linux/spinlock.h:56,
                 from ./include/linux/mmzone.h:8,
                 from ./include/linux/gfp.h:7,
                 from arch/arm64/mm/dma-mapping.c:7:
./include/asm-generic/bitops/generic-non-atomic.h:105:1: error: function declaration isn't a prototype [-Werror=strict-prototypes] ./include/asm-generic/bitops/generic-non-atomic.h: In function 'generic___test_and_change_bit': ./include/asm-generic/bitops/generic-non-atomic.h:105:39: error: expected declaration specifiers before ')' token ./include/asm-generic/bitops/generic-non-atomic.h:111:205: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:111:663: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:111:1211: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:111:1656: error: expected '=', ',', ';', 'asm' or '__attribute__' before string constant ./include/asm-generic/bitops/generic-non-atomic.h:111:1670: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:111:1694: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:111:1719: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:111:1745: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:111:1773: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:111:1789: error: invalid suffix "b" on integer constant ./include/asm-generic/bitops/generic-non-atomic.h:111:1791: error: stray '\' in program ./include/asm-generic/bitops/generic-non-atomic.h:112:652: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:112:1193: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:112:1726: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token ./include/asm-generic/bitops/generic-non-atomic.h:131:47: warning: file "./include/asm-generic/bitops/hweight.h" linemarker ignored due to incorrect nesting
```

Would go pumping mode change the preprocessing problem?

Or should I even try clang instead?

Thanks,
Qu


czw., 26 sty 2023 o 04:02 Qu Wenruo via distcc <distcc@lists.samba.org <mailto: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 <http://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 <http://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
    <http://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/ <http://distcc.samba.org/>
    To unsubscribe or change options:
    https://lists.samba.org/mailman/listinfo/distcc
    <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

Reply via email to