<div dir="ltr"><div>Hi Jiri,</div><div><br></div><div>Okay, I commented out that header on my Windows 10 machine (Version 20H2, 19042.685) and it compiled.</div><div><br></div><div>That error was on a different Linux machine when cross compiling the cross toolchain for Windows (i686 rtems6-arm worked now, so that's nice). Maybe this #define is also derived from the current OS?</div><div>I could try to supply it manually..</div><div><br></div><div>Kind Regards</div><div>Robin<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 18 Dec 2020 at 16:35, Jiri Gaisler <<a href="mailto:jiri@gaisler.se" target="_blank">jiri@gaisler.se</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p><br>
</p>
<div>On 12/18/20 2:10 PM, Robin Müller
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>In case you're interested, this is the fail report for
the SIS Cxc build on Linux (failed both for i686 and
x86_64).</div>
<div><br>
</div>
<div>I think it fails because _WIN32_WINNT (windows version)
is not defined, causing winsock2.h to exclude requires
sections.</div>
<div><br>
</div>
<div>Build command was:</div>
<div> ../source-builder/sb-set-builder
--prefix=/c/Users/Robin/RTEMS/rtems-tools/rtems/6
--no-install --bset-tar-file --host=i686-w64-mingw32
6/rtems-sparc<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>I had a quick look at this. The first problem with missing
arpa/inet.h can be fixed by commenting out the include file, as it
is not needed:<br>
</p>
<p>i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -DFAST_UART -O2 -g
-pipe
-I/home/rmueller/Documents/RTEMS/rtems-tools/src/rsb/rtems/build/tmp/sb-1000/6/rtems-sparc/c/Users/Robin/RTEMS/rtems-tools/rtems/6/include
-MT greth.o -MD -MP -MF .deps/greth.Tpo -c -o greth.o greth.c<br>
greth.c:31:10: fatal error: arpa/inet.h: No such file or directory<br>
31 | #include <arpa/inet.h><br>
</p>
<p><br>
</p>
<p>The second problem with winsock2.h is not obvious to me. On my
old windows7/qemu system, remote.c compiles fine and winsock2.h
provides the necessary defines. Which windows version are you
using where it fails?</p>
<p>I am about to release a new sis version with more RISCV support,
so I could add fixes for MSYS2 if necessary ...<br>
</p>
<p>Regards, Jiri.<br>
</p>
<p><br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Kind Regards</div>
<div>Robin<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 18 Dec 2020 at 12:49,
Robin Müller <<a href="mailto:robin.mueller.m@gmail.com" target="_blank">robin.mueller.m@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>If I understand correctly, the BSPs can be installed
with waf only if the tool suite for the given architecture
has been installed.<br>
</div>
<div>Problem is, the RSB build will fail even if a tiny
component is problematic. <br>
</div>
<div>I thought the tool suite itself is installed using the
build commands required by the sources (make, automake,
etc). <br>
</div>
<div>Is it possible to also build these sources with waf?</div>
<div><br>
</div>
<div>I have tried this cross compiling on linux for windows
(I used x86_64 instead of i686) because everything was
working on Linux, but there are issues with the SIS tool
for sparc-rtems6..</div>
<div>But SIS is now also problematic on the Windows machine
where I almost managed to build everything.</div>
<div><br>
</div>
<div>Everything except SIS was built by the RSB and I copied
the installed files manually to install them and tried to
build a BSP (is there actually some script like do-install
which will perform this step?)<br>
</div>
<div>But now some RTEMS tool is missing (rtems-bin2c):</div>
<div><br>
</div>
<div>$ ./waf configure --prefix=$RTEMS_TOOLS
--rtems-bsp=sparc/erc32<br>
Setting top to :
C:/Users/Robin/Documents/RTEMS/rtems-tools/src/rtems<br>
Setting out to :
C:/Users/Robin/Documents/RTEMS/rtems-tools/src/rtems/build<br>
Configure board support package (BSP) : sparc/erc32<br>
Checking for program 'sparc-rtems6-gcc' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-gcc.exe<br>
Checking for program 'sparc-rtems6-g++' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-g++.exe<br>
Checking for program 'sparc-rtems6-ar' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ar.exe<br>
Checking for program 'sparc-rtems6-ld' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ld.exe<br>
Checking for program 'ar' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ar.exe<br>
Checking for program 'g++, c++' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-g++.exe<br>
Checking for program 'ar' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ar.exe<br>
Checking for program 'gas, gcc' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-gcc.exe<br>
Checking for program 'ar' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ar.exe<br>
Checking for program 'gcc, cc' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-gcc.exe<br>
Checking for program 'ar' :
C:/Users/Robin/Documents/RTEMS/rtems-tools/rtems/6/bin/sparc-rtems6-ar.exe<br>
Checking for program 'rtems-bin2c' : not found<br>
Could not find the program ['rtems-bin2c']<br>
(complete log in
C:/Users/Robin/Documents/RTEMS/rtems-tools/src/rtems/build/config.log)</div>
<div><br>
</div>
<div>In general the build process on Windows seems to be
more "brittle" than on Linux, so maybe installers would be
a good idea? I generally installed cross-compilers (e.g.
arm-none-eabi-gcc) on Windows <br>
</div>
<div>using installers (for example <a href="https://xpack.github.io/arm-none-eabi-gcc/" target="_blank">https://xpack.github.io/arm-none-eabi-gcc/</a>)
and have made very good experience with that.<br>
</div>
<div><br>
</div>
<div>Kind Regards</div>
<div>Robin<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 18 Dec 2020 at
12:24, Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a>>
wrote:<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 18/12/2020 11:35,
Chris Johns wrote:<br>
<br>
>> Since all parts of RTEMS build now with waf I
think it is possible to build RTEMS applications on
Windows without having to install MSYS2/MinGW. It should
work with only a Python installation, but I haven't tested
this yet.<br>
> This maybe true In theory but I have not been able to
achieve it.<br>
What was the missing piece?<br>
<br>
-- <br>
embedded brains GmbH<br>
Herr Sebastian HUBER<br>
Dornierstr. 4<br>
82178 Puchheim<br>
Germany<br>
email: <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a><br>
phone: +49-89-18 94 741 - 16<br>
fax: +49-89-18 94 741 - 08<br>
<br>
Registergericht: Amtsgericht München<br>
Registernummer: HRB 157899<br>
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen,
Thomas Dörfler<br>
Unsere Datenschutzerklärung finden Sie hier:<br>
<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote>
</div>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
devel mailing list
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>
<a href="http://lists.rtems.org/mailman/listinfo/devel" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></pre>
</blockquote>
</div>
</blockquote></div>