Re: OS X Build Problems tag 5.2 ->Invalid configuration `arm64-apple-darwin22.3.0': machine `arm64-apple' not recognized

2023-03-29 Thread Chris Johns
On 30/3/2023 3:06 am, Heinz Junkes wrote: > Hi, > > I have, once again, a problem with building RTEMS on OS X. > > It works fine with rtems6/master > > with clang 10.0.0 , python 3.8.5 on > Darwin Judiciary-Pag.fritz.box 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov > 11 02:04:44 PST 2022;

Re: Error in building rtems 5.3 tools via mingw

2023-03-29 Thread Chris Johns
On 29/3/2023 9:11 pm, Giovanni Righi wrote: > Ok, also I forgot to say in the previous email that I'm using windows 11.  Ah thanks. I have access to a Windows 11 machine. Chris ___ users mailing list users@rtems.org

OS X Build Problems tag 5.2 ->Invalid configuration `arm64-apple-darwin22.3.0': machine `arm64-apple' not recognized

2023-03-29 Thread Heinz Junkes
Hi, I have, once again, a problem with building RTEMS on OS X. It works fine with rtems6/master with clang 10.0.0 , python 3.8.5 on Darwin Judiciary-Pag.fritz.box 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103 arm64 python shows:

Re: Error in building rtems 5.3 tools via mingw

2023-03-29 Thread Giovanni Righi
Ok, also I forgot to say in the previous email that I'm using windows 11. Il giorno mer 29 mar 2023 alle ore 10:42 Chris Johns ha scritto: > On 29/3/2023 6:33 pm, Giovanni Righi wrote: > > I tried again with the flag --jobs=1 on a clean build and I got the same > error > > message. > > Thanks >

Re: Error in building rtems 5.3 tools via mingw

2023-03-29 Thread Chris Johns
On 29/3/2023 6:33 pm, Giovanni Righi wrote: > I tried again with the flag --jobs=1 on a clean build and I got the same error > message. Thanks > 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,

Re: Error in building rtems 5.3 tools via mingw

2023-03-29 Thread Giovanni Righi
I tried again with the flag --jobs=1 on a clean build and I got the same error message. 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