Looks like some distcc or ccache bug / regression.

However, for distcc you need to run the identical t2 compiler on your cluster, 
otherwise you can random compiler results mixed together and likely exhibiting 
random bugs but in any case results different from what they should be from 
using the t2 compiler Version and configuration.

I have not used distcc for nearly 20 years…

Sent on the go - http://ExactCODE.com Germany.

> On 25. Jul 2022, at 13:30, Roger Mason <rma...@mun.ca> wrote:
> 
> hello,
> 
> René Rebe <r...@exactcode.com> writes:
> 
>> 
>> 
>> 
>> indeed, as we can’t fully cross build perl (we probably should work on that) 
>> you currently
>> need to install (emerge) it into your freshly installed system to build a 
>> whole new target
>> from scratch, e.g. using something like scripts/Emerge-Pkg -missing=only 
>> perl perl-xml-parser
>> (or something like that —typos).
>> 
>> Maybe we should natively bootstrap that for target builds to avoid ans such 
>> “non-standard”
>> host system requirements, ...
> 
> Thanks, that got me past that bump.  Now I'm running into this:
> 
> 08:49:41 Building 1-kernel/linux-header (5.1)
>  Compiler Cache enabled: 0.00% cache hits so far
>  Building in src.linux-header.system.20220725.084940.31466.hedenbergite, with 
> 4 threads
>  Writing output to $root/var/adm/logs/1-linux-header.out
> gawk: cmd. line:4:                      END { hit-=0; miss-=;
> gawk: cmd. line:4:                                          ^ syntax error
>  Compiler Cache Hits while pkg build: 
> /root/t2-trunk/target/desktop/pkg-header% (0 hits,  misses)
> ! Aborted (core dumped)
> ! Aborted (core dumped)
> ! Aborted (core dumped)
> ! Aborted (core dumped)
> ! Aborted (core dumped)
> ! Aborted (core dumped)
> ! Due to previous errors, no 1-linux-header.log file!
> ! (Try enabling xtrace in the config to track an error inside the build 
> system.)
>  +00:00:41 Aborted building kernel/linux-header
>  Unmounting loop mounts ...
> 
> When I enter src.linux-header.system.20220725.084940.31466... and run
> 'eval $MAKE $makeopts' I get asked questions that ISTR may be be kernel
> config options.  Mostly I don't understand the questions, so is there
> some way to set them to a default answer?
> 
> Another question.  I have distcc set up in the config, but the worker
> (Fedora 36) never does any of the work.  Is the T2 distcc setup to use
> SSH or does it use TCP?
> 
> Thanks,
> Roger

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
li...@t2-project.org with a subject of: unsubscribe t2

Reply via email to