<div dir="ltr"><div><div>I tried again with the flag --jobs=1 on a clean build and I got the same error message.<div>But this time it seems to happen on the second file. My idea is that with parallel building it managed to build more files before getting the error, while with only one job it's slower so it gets the error earlier.</div><div>Here's the tail of the log:<br>___________________________________________________________________________________<br><div>+ ./waf distclean configure --prefix=/c/opt/rtems/5.3<br>'distclean' finished successfully (0.000s)<br>Setting top to : C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3 <br>Setting out to : C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/build <br>Version : 5.3 (5) <br>Checking for program 'python' : C:/msys64/mingw64/bin/python.exe <br>Checking for python version >= 2.6.6 : 3.10.10 <br>Checking for program 'python' : C:/msys64/mingw64/bin/python.exe <br>Checking for program 'python2' : C:\msys64\mingw64\bin/python2.exe <br>Checking for program 'python3' : C:\msys64\mingw64\bin/python3.exe <br>Checking for 'gcc' (C compiler) : C:\msys64\mingw64\bin/gcc.exe <br>Checking for 'g++' (C++ compiler) : C:\msys64\mingw64\bin/g++.exe <br>Checking for header alloca.h : not found <br>Checking for header fcntl.h : yes <br>Checking for header process.h : yes <br>Checking for header stdlib.h : yes <br>Checking for header string.h : yes <br>Checking for header strings.h : yes <br>Checking for header sys/file.h : yes <br>Checking for header sys/stat.h : yes <br>Checking for header sys/time.h : yes <br>Checking for header sys/types.h : yes <br>Checking for header sys/wait.h : not found <br>Checking for header unistd.h : yes <br>Checking for header vfork.h : not found <br>Checking for getrusage : no <br>Checking for program 'm4' : C:\msys64\usr\bin/m4.exe <br>Checking for header sys/wait.h : not found <br>Checking for kill : no <br>Checking for 'gcc' (C compiler) : C:\msys64\mingw64\bin/gcc.exe <br>Checking for 'g++' (C++ compiler) : C:\msys64\mingw64\bin/g++.exe <br>Checking for 'gcc' (C compiler) : C:\msys64\mingw64\bin/gcc.exe <br>Checking for strnlen : yes <br>Checking for 'g++' (C++ compiler) : C:\msys64\mingw64\bin/g++.exe <br>Checking for fopen64 : no <br>Checking for stat64 : yes <br>Checking for 'gcc' (C compiler) : C:\msys64\mingw64\bin/gcc.exe <br>Checking for 'g++' (C++ compiler) : C:\msys64\mingw64\bin/g++.exe <br>Checking for library LLVM : not found <br>Checking for header zlib.h : yes <br>Checking for library z : yes <br>Checking for library ws2_32 : yes <br>Checking for compiler flags -std=c++14 : yes <br>'configure' finished successfully (12.090s)<br>+ ./waf<br>Waf: Entering directory `C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/build'<br>[ 1/258] Compiling rtemstoolkit/elftoolchain/libelf/libelf_convert.m4<br>Traceback (most recent call last):<br> File "<string>", line 55, in <module><br> File "<string>", line 20, in run<br>[ 2/258] Compiling rtemstoolkit/elftoolchain/libelf/libelf_fsize.m4<br>OSError: [Errno 22] Invalid argument<br>Waf: Leaving directory `C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/build'<br>Build failed<br>Traceback (most recent call last):<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Context.py", line 181, in exec_command<br> ret,out,err=Utils.run_process(cmd,kw,cargs)<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Utils.py", line 598, in run_process<br> return run_prefork_process(cmd,kwargs,cargs)<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Utils.py", line 533, in run_prefork_process<br> proc.stdin.write(obj)<br>BrokenPipeError: [Errno 32] Broken pipe<br><br>During handling of the above exception, another exception occurred:<br><br>Traceback (most recent call last):<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py", line 180, in process<br> ret=self.run()<br> File "<string>", line 14, in f<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py", line 173, in exec_command<br> return self.generator.bld.exec_command(cmd,**kw)<br> File "C:/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/rtems-tools-5.3/waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Context.py", line 183, in exec_command<br> raise Errors.WafError('Execution failure: %s'%str(e),ex=e)<br>waflib.Errors.WafError: Execution failure: [Errno 32] Broken pipe<br><br>shell cmd failed: sh -ex /c/opt/rtems/rtems-source-builder-5.3/rtems/build/rt51/do-build<br>error: building rt51</div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno sab 25 mar 2023 alle ore 00:06 Chris Johns <<a href="mailto:chrisj@rtems.org">chrisj@rtems.org</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 23/3/2023 10:48 pm, Giovanni Righi wrote:<br>
> Ok so I tried what you suggested, I downloaded the rtems-tools-5.3 tar form the<br>
> server and I launched directly the waf script.<br>
> I got the same error, then I tried again and again I got the same error but on a<br>
> file following the one that caused the first error. So I launched the waf again<br>
> and it managed to compile all the files.<br>
> After this I did a waf clean and tried again and I got the same results, error -<br>
> error - compilation complete.<br>
> Note the two errors happened in the same files as the first "run".<br>
> So now I have the tools compiled but I don't know how to finish the build of the<br>
> toolchain, because if I launch the sb-set-builder again it cleans everything and<br>
> starts again so when it reaches the tools part it crashes again because of the<br>
> waf error.<br>
> I hope the explanation is clear and there is a solution for this problem. <br>
> I attach a file with parts of the three runs so you can see what's going on.<br>
<br>
Thanks. I wonder if the scripting used to handle the `.m4` files is broken on<br>
mingw? What happens if you add --jobs=1 to a clean build?<br>
<br>
What version of Windows?<br>
<br>
Chris<br>
</blockquote></div>