On 19/12/20 9:51 pm, Robin Müller wrote:
> Thanks for the quick fix. I was able to build sparc-rtems6 on the Windows
> machine with the fix.
Thank you for letting us know.
> So basically, arm-rtesm6 is still problematic because of the missing headers
> (but worked on Linux using Canadian Cross Co
Hi Jiri,
Thanks for the quick fix. I was able to build sparc-rtems6 on the Windows
machine with the fix.
So basically, arm-rtesm6 is still problematic because of the missing
headers (but worked on Linux using Canadian Cross Compiling) but with
sparc-rtems6 it's the other way around, it works on W
On 18/12/20 10:24 pm, Sebastian Huber wrote:
> On 18/12/2020 11:35, Chris Johns wrote:
>
>>> 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
On 12/18/20 5:15 PM, Robin Müller wrote:
> Hi Jiri,
>
> Okay, I commented out that header on my Windows 10 machine (Version 20H2,
> 19042.685) and it compiled.
>
> That error was on a different Linux machine when cross compiling the cross
> toolchain for Windows (i686 rtems6-arm worked now, so t
Hi Jiri,
Okay, I commented out that header on my Windows 10 machine (Version 20H2,
19042.685) and it compiled.
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
On 12/18/20 2:10 PM, Robin Müller wrote:
> In case you're interested, this is the fail report for the SIS Cxc build on
> Linux (failed both for i686 and x86_64).
>
> I think it fails because _WIN32_WINNT (windows version) is not defined,
> causing winsock2.h to exclude requires sections.
>
> Bui
In case you're interested, this is the fail report for the SIS Cxc build on
Linux (failed both for i686 and x86_64).
I think it fails because _WIN32_WINNT (windows version) is not defined,
causing winsock2.h to exclude requires sections.
Build command was:
../source-builder/sb-set-builder
--pref
If I understand correctly, the BSPs can be installed with waf only if the
tool suite for the given architecture has been installed.
Problem is, the RSB build will fail even if a tiny component is
problematic.
I thought the tool suite itself is installed using the build commands
required by the sour
On 18/12/2020 11:35, Chris Johns wrote:
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.
This maybe true In theory but
> On 18 Dec 2020, at 5:54 pm, Sebastian Huber
> wrote:
>
> Hello Robin,
>
> my experience over the years with MSYS2 is that building GCC is always
> painful and a waste of time.
This is a bit harsh and I do not fully agree it is a waste of time. MSYS has
proven to be an OK solution. Not pe
Hello Robin,
my experience over the years with MSYS2 is that building GCC is always
painful and a waste of time. What works quite reliably is building the
RTEMS tools with a i686-w64-mingw32 cross-compiler on Linux. Most
distributions include a standard package for this.
Since all parts of R
Hi,
The RSB was updasted because there were some issues with GMP and I tested
whether this also fixed my MSYS2 build process for the RTEMS tools.
I now get a header file missing error when building newlib:
Making all in arm
In file included from
../../../../../../../../../../gnu-mirror-gcc-1cd
12 matches
Mail list logo
