Re: [PATCH rtems-docs] user/exe: Add MicroBlaze to Dynamic Loader architecture list

2023-10-05 Thread Chris Johns 
OK

Chris

On 6/10/2023 5:40 am, Alex White wrote:
> ---
>  user/exe/loader.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/user/exe/loader.rst b/user/exe/loader.rst
> index be2e78e..fdc54a8 100644
> --- a/user/exe/loader.rst
> +++ b/user/exe/loader.rst
> @@ -844,6 +844,7 @@ The following architectures are supported:
>   - Intel x86 (i386)
>   - LM32
>   - M68K
> + - MicroBlaze
>   - MIPS
>   - Moxie
>   - PowerPC
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

External document links (was Re: Add Formal Verification chapter v4)

2023-10-05 Thread Chris Johns 
On 6/10/2023 1:02 am, Gedare Bloom wrote:
> On Fri, Sep 22, 2023 at 4:50 AM andrew.butterfi...@scss.tcd.ie
>  wrote:
>> Also, I'm not sure the best way to refer to a sub-section of another document
>> I used something like (See Host Tools in the RTEMS User Manual)
>> I guessed the URL might be less robust
> Yes this is basically correct. We don't want explicit links between
> documents. It's a bit challenging at the moment to validate
> cross-document references and we don't have a great solution or
> standard approach for how to do it.

There are a few issues having external links between our documents:

1. The links reference the `master` branch so branching for a release breaks the
documentation in a releases and that is something we cannot have.

2. PDF documents do not know how to link to the other PDF documents. A PDF is
not web resource.

3. Localised builds for internal use, for example on a disk or local server
still link externally back to `master`. If you need to work on a site that does
not have internet access the documentation breaks.

With the current documentation structure these issue are beyond the scope for us
to deal with in sphinx. We develop an RTOS.

A single book of all our documents would resolve this but that would slow the
documentation builds down unless someone knows how to build partial pieces.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Avoid StopIteration exception for non-rtems .pc

2023-10-05 Thread Chris Johns 
Hi Martin,

Thanks for posting the patch. I have pushed it. I have pushed an update after
running the change through yapf. I forgot to do that before pushing.

I will also add a new function to the rtems module as a separate patch:

+def arch_bsp(ctx):
+""" Return the list of arch/bsps we are building."""
+return ctx.env.ARCH_BSP
+
+

I think it would be good to update all the submodules.

On 5/10/2023 11:40 pm, Martin Erik Werner wrote:
> _arch_from_arch_bsp() and _bsp_from_arch_bsp() has overly optimistic
> assumptions that the argument must contain a '-'-separated field which
> starts with "rtems". These functions are intended to find the target
> triplet or the bsp parts of strings like "sparc-gaisler-rtems5-leon3"
> and "arm-rtems6-xilinx_zynq_zc702"

Yes the interface around arch/bsp is a bit average and I have wondered about a
change but I think the interface is now set and I think it is too late to 
change.

> But _find_installed_arch_bsps() may call _arch_from_arch_bsp() with the
> name (without file extension) of any file which ends with ".pc",
> including for example "expat". This triggers a StopIteration exception
> when trying to find the next field after the "rtems" field, since no
> "rtems" field exists to start with.
> 
> Rework these function to remove the preconditions, so that they return
> None if no "rtems" field exist or if no field exists before or after the
> "rtems" field.

Nice.

> It could be argued. based on their name, that calling these functions
> with something that is not a triplet-bsp string is incorrect to start
> with, but attempting to address that is not done here.

Yes I agree and I also think we need to accept the string in this case.

Chris

> ---
> 
> This should fix the issue discovered by David Siddons and Frank Kühndel
> described in the "build failed" thread from 2023-07-23 in the
> rtems-users mailing list with message-id:
> <8e6c2841-ae9e-aacf-de84-e6340d204...@embedded-brains.de>
> 
> I have tested this fix when compiling the simple quickstart application
> for the sparc-gaisler-rtems5-leon3 and arm-rtems6-xilinx_zynq_zc702
> targets, but I have not verified execution of the build results, this is
> probably the amount of testing that I will be able to perform at the
> moment.
> 
>  rtems.py | 14 --
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/rtems.py b/rtems.py
> index c65a7d2..a29d281 100644
> --- a/rtems.py
> +++ b/rtems.py
> @@ -859,15 +859,17 @@ def _check_arch_bsps(req, config, path, archs, version):
>  
>  def _arch_from_arch_bsp(arch_bsp):
>  fields = arch_bsp.split('-')
> -rtems_field_index = next(i for i, field in enumerate(fields) if 
> field.startswith('rtems'))
> -return '-'.join(fields[:(rtems_field_index + 1)])
> -
> +for i, field in enumerate(fields):
> +if field.startswith('rtems') and fields[:(i + 1)] is not None:
> +return '-'.join(fields[:(i + 1)])
> +return None
>  
>  def _bsp_from_arch_bsp(arch_bsp):
>  fields = arch_bsp.split('-')
> -rtems_field_index = next(i for i, field in enumerate(fields) if 
> field.startswith('rtems'))
> -return '-'.join(fields[(rtems_field_index + 1):])
> -
> +for i, field in enumerate(fields):
> +if field.startswith('rtems') and fields[(i + 1):] is not None:
> +return '-'.join(fields[(i + 1):])
> +return None
>  
>  def _pkgconfig_path(path):
>  return os.path.join(path, 'lib', 'pkgconfig')
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs] user/exe: Add MicroBlaze to Dynamic Loader architecture list

2023-10-05 Thread Alex White 
---
 user/exe/loader.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/user/exe/loader.rst b/user/exe/loader.rst
index be2e78e..fdc54a8 100644
--- a/user/exe/loader.rst
+++ b/user/exe/loader.rst
@@ -844,6 +844,7 @@ The following architectures are supported:
  - Intel x86 (i386)
  - LM32
  - M68K
+ - MicroBlaze
  - MIPS
  - Moxie
  - PowerPC
-- 
2.34.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Add Formal Verification chapter v4

2023-10-05 Thread Gedare Bloom 
On Fri, Sep 22, 2023 at 4:50 AM andrew.butterfi...@scss.tcd.ie
 wrote:
>
>
>
> 
> Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204
> Lero@TCD, Head of Software Foundations & Verification Research Group
> School of Computer Science and Statistics,
> Room G.39, O'Reilly Institute, Trinity College, University of Dublin
> http://www.scss.tcd.ie/Andrew.Butterfield/ 
> 
> 
>
>
>
>
> From: "andrew.butterfi...@scss.tcd.ie 
> "  >
> Date: Thursday 21 September 2023 at 17:02
>
> >On 21/09/2023, 16:42, "Sebastian Huber"  > 
> >> >>> wrote:
> >On 21.09.23 17:41, Gedare Bloom wrote:
> >>> On Thu, Sep 21, 2023 at 9:36 AM Sebastian Huber
> >>>  >>>  
> >>>  >>> >> wrote:
>  On 21.09.23 17:28, Gedare Bloom wrote:
> > I've taken a look and resolved / commented. We can leave some of the
> > `sis` specific bits, with the understanding that hopefully the
> > simulation target can be made more generic in the future. This could be
> > a potential GSoC project for Prequalification to hook it up to
> > `rtems-tools.git/tester` to make use of the capabilities we already have
> > for running simulators.
>  The model based tests are not target-specific. You could run them with
>  any (simulator) BSP.
> 
> >>> Yes, I suspected that. However, the documentation is currently written
> >>> toward sis. It may be better to point the reader to another doc that
> >>> explains how to run tests, such as
> >>> https://docs.rtems.org/branches/master/user/tools/tester.html 
> >>>  
> >>>  
> >>> ;>
> >>>
> >>> I don't recall any documentation that discusses simulator targets 
> >>> specifically.
> >>Yes, we should not duplicate this documentation. This is not maintainable.
> >
> >I can remove all references to `sis` from the documentation and point to 
> >tester.html
> >However note that the python sources for all of this, in 
> >rtems-central/formal/promela/src
> >we have explicit references in testbuilder-template.yml to `simulator: 
> >/sparc-rtems6-sis`
> >I guess that needs to be changed.
>
> I've referred to the RTEMS Tester, (replacing `sis`),
> and also just noted that the default template for testbuilder refers to `sis`
>
> Also, I'm not sure the best way to refer to a sub-section of another document
> I used something like (See Host Tools in the RTEMS User Manual)
> I guessed the URL might be less robust
Yes this is basically correct. We don't want explicit links between
documents. It's a bit challenging at the moment to validate
cross-document references and we don't have a great solution or
standard approach for how to do it.

>
> Andrew
> 
> Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204
> Lero@TCD, Head of Software Foundations & Verification Research Group
> School of Computer Science and Statistics,
> Room G.39, O'Reilly Institute, Trinity College, University of Dublin
> http://www.scss.tcd.ie/Andrew.Butterfield/ 
>  
>  
> ;>
> 
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embedded-brains.de 
>  
>  >
> phone: +49-89-18 94 741 - 16
> fax: +49-89-18 94 741 - 08
>
>
>
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/ 
>  
>  
> ;>
>
>
>
>
>
>
>
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [net-legacy PATCH] tests: Add header for RTEMS test printer

2023-10-05 Thread Gedare Bloom 
OK

On Wed, Oct 4, 2023 at 4:13 PM  wrote:
>
> From: Chris Johns 
>
> ---
>  libtest/testbeginend.c | 1 +
>  libtest/testwrappers.c | 1 +
>  testsuites/loopback/init.c | 1 +
>  testsuites/pppd/init.c | 4 +++-
>  4 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/libtest/testbeginend.c b/libtest/testbeginend.c
> index 89b2468..83f1d3c 100644
> --- a/libtest/testbeginend.c
> +++ b/libtest/testbeginend.c
> @@ -19,6 +19,7 @@
>  #endif
>
>  #include 
> +#include 
>  #include 
>  #include 
>
> diff --git a/libtest/testwrappers.c b/libtest/testwrappers.c
> index 9679f75..052ebf8 100644
> --- a/libtest/testwrappers.c
> +++ b/libtest/testwrappers.c
> @@ -11,6 +11,7 @@
>  #endif
>
>  #include 
> +#include 
>
>  int __wrap_printf(const char* format, ...);
>  int __wrap_puts(const char *str);
> diff --git a/testsuites/loopback/init.c b/testsuites/loopback/init.c
> index 891225c..d2aafcc 100644
> --- a/testsuites/loopback/init.c
> +++ b/testsuites/loopback/init.c
> @@ -8,6 +8,7 @@
>  #include "config.h"
>  #endif
>
> +#include 
>  #include 
>
>  const char rtems_test_name[] = "LOOPBACK";
> diff --git a/testsuites/pppd/init.c b/testsuites/pppd/init.c
> index 95e0d53..12a57e0 100644
> --- a/testsuites/pppd/init.c
> +++ b/testsuites/pppd/init.c
> @@ -21,9 +21,11 @@
>  #include 
>  #include 
>  #include 
> -#include "netconfig.h"
> +#include 
>  #include 
>
> +#include "netconfig.h"
> +
>  const char rtems_test_name[] = "PPPD";
>
>  static void notification(int fd, int seconds_remaining, void *arg)
> --
> 2.37.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Avoid StopIteration exception for non-rtems .pc

2023-10-05 Thread Gedare Bloom 
LGTM

On Thu, Oct 5, 2023 at 7:40 AM Martin Erik Werner
 wrote:
>
> _arch_from_arch_bsp() and _bsp_from_arch_bsp() has overly optimistic
> assumptions that the argument must contain a '-'-separated field which
> starts with "rtems". These functions are intended to find the target
> triplet or the bsp parts of strings like "sparc-gaisler-rtems5-leon3"
> and "arm-rtems6-xilinx_zynq_zc702"
>
> But _find_installed_arch_bsps() may call _arch_from_arch_bsp() with the
> name (without file extension) of any file which ends with ".pc",
> including for example "expat". This triggers a StopIteration exception
> when trying to find the next field after the "rtems" field, since no
> "rtems" field exists to start with.
>
> Rework these function to remove the preconditions, so that they return
> None if no "rtems" field exist or if no field exists before or after the
> "rtems" field.
>
> It could be argued. based on their name, that calling these functions
> with something that is not a triplet-bsp string is incorrect to start
> with, but attempting to address that is not done here.
> ---
>
> This should fix the issue discovered by David Siddons and Frank Kühndel
> described in the "build failed" thread from 2023-07-23 in the
> rtems-users mailing list with message-id:
> <8e6c2841-ae9e-aacf-de84-e6340d204...@embedded-brains.de>
>
> I have tested this fix when compiling the simple quickstart application
> for the sparc-gaisler-rtems5-leon3 and arm-rtems6-xilinx_zynq_zc702
> targets, but I have not verified execution of the build results, this is
> probably the amount of testing that I will be able to perform at the
> moment.
>
>  rtems.py | 14 --
>  1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/rtems.py b/rtems.py
> index c65a7d2..a29d281 100644
> --- a/rtems.py
> +++ b/rtems.py
> @@ -859,15 +859,17 @@ def _check_arch_bsps(req, config, path, archs, version):
>
>  def _arch_from_arch_bsp(arch_bsp):
>  fields = arch_bsp.split('-')
> -rtems_field_index = next(i for i, field in enumerate(fields) if 
> field.startswith('rtems'))
> -return '-'.join(fields[:(rtems_field_index + 1)])
> -
> +for i, field in enumerate(fields):
> +if field.startswith('rtems') and fields[:(i + 1)] is not None:
> +return '-'.join(fields[:(i + 1)])
> +return None
>
>  def _bsp_from_arch_bsp(arch_bsp):
>  fields = arch_bsp.split('-')
> -rtems_field_index = next(i for i, field in enumerate(fields) if 
> field.startswith('rtems'))
> -return '-'.join(fields[(rtems_field_index + 1):])
> -
> +for i, field in enumerate(fields):
> +if field.startswith('rtems') and fields[(i + 1):] is not None:
> +return '-'.join(fields[(i + 1):])
> +return None
>
>  def _pkgconfig_path(path):
>  return os.path.join(path, 'lib', 'pkgconfig')
> --
> 2.30.2
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Avoid StopIteration exception for non-rtems .pc

2023-10-05 Thread Frank Kühndel 

Hello Martin,

thanks for the fix. Your patch works for me. I tried with

$ ./waf configure --rtems=/opt/rtems/6 
--rtems-bsp=arm/xilinx_zynq_a9_qemu


$ ./waf

$ env QEMU_AUDIO_DRV="none" qemu-system-arm -no-reboot -net none -m 
256M -serial null -serial mon:stdio -nographic -M xilinx-zynq-a9 -kernel 
build/arm-rtems6-xilinx_zynq_a9_qemu/hello.exe


The hello world executable I used runs fine.

Many thanks again,
fk

On 10/5/23 15:40, Martin Erik Werner wrote:

Subject:
[PATCH] Avoid StopIteration exception for non-rtems .pc
From:
Martin Erik Werner 
Date:
10/5/23, 15:40

To:
devel@rtems.org
CC:
chr...@rtems.org, sidd...@bnl.gov, frank.kuehn...@embedded-brains.de


_arch_from_arch_bsp() and _bsp_from_arch_bsp() has overly optimistic
assumptions that the argument must contain a '-'-separated field which
starts with "rtems". These functions are intended to find the target
triplet or the bsp parts of strings like "sparc-gaisler-rtems5-leon3"
and "arm-rtems6-xilinx_zynq_zc702"

But _find_installed_arch_bsps() may call _arch_from_arch_bsp() with the
name (without file extension) of any file which ends with ".pc",
including for example "expat". This triggers a StopIteration exception
when trying to find the next field after the "rtems" field, since no
"rtems" field exists to start with.

Rework these function to remove the preconditions, so that they return
None if no "rtems" field exist or if no field exists before or after the
"rtems" field.

It could be argued. based on their name, that calling these functions
with something that is not a triplet-bsp string is incorrect to start
with, but attempting to address that is not done here.
---

This should fix the issue discovered by David Siddons and Frank Kühndel
described in the "build failed" thread from 2023-07-23 in the
rtems-users mailing list with message-id:
<8e6c2841-ae9e-aacf-de84-e6340d204...@embedded-brains.de>

I have tested this fix when compiling the simple quickstart application
for the sparc-gaisler-rtems5-leon3 and arm-rtems6-xilinx_zynq_zc702
targets, but I have not verified execution of the build results, this is
probably the amount of testing that I will be able to perform at the
moment.

  rtems.py | 14 --
  1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/rtems.py b/rtems.py
index c65a7d2..a29d281 100644
--- a/rtems.py
+++ b/rtems.py
@@ -859,15 +859,17 @@ def _check_arch_bsps(req, config, path, archs, version):
  
  def _arch_from_arch_bsp(arch_bsp):

  fields = arch_bsp.split('-')
-rtems_field_index = next(i for i, field in enumerate(fields) if 
field.startswith('rtems'))
-return '-'.join(fields[:(rtems_field_index + 1)])
-
+for i, field in enumerate(fields):
+if field.startswith('rtems') and fields[:(i + 1)] is not None:
+return '-'.join(fields[:(i + 1)])
+return None
  
  def _bsp_from_arch_bsp(arch_bsp):

  fields = arch_bsp.split('-')
-rtems_field_index = next(i for i, field in enumerate(fields) if 
field.startswith('rtems'))
-return '-'.join(fields[(rtems_field_index + 1):])
-
+for i, field in enumerate(fields):
+if field.startswith('rtems') and fields[(i + 1):] is not None:
+return '-'.join(fields[(i + 1):])
+return None
  
  def _pkgconfig_path(path):

  return os.path.join(path, 'lib', 'pkgconfig')
-- 2.30.2



--
embedded brains GmbH & Co. KG
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11

Registergericht: Amtsgericht München
Registernummer: HRA 117265
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] Avoid StopIteration exception for non-rtems .pc

2023-10-05 Thread Martin Erik Werner 
_arch_from_arch_bsp() and _bsp_from_arch_bsp() has overly optimistic
assumptions that the argument must contain a '-'-separated field which
starts with "rtems". These functions are intended to find the target
triplet or the bsp parts of strings like "sparc-gaisler-rtems5-leon3"
and "arm-rtems6-xilinx_zynq_zc702"

But _find_installed_arch_bsps() may call _arch_from_arch_bsp() with the
name (without file extension) of any file which ends with ".pc",
including for example "expat". This triggers a StopIteration exception
when trying to find the next field after the "rtems" field, since no
"rtems" field exists to start with.

Rework these function to remove the preconditions, so that they return
None if no "rtems" field exist or if no field exists before or after the
"rtems" field.

It could be argued. based on their name, that calling these functions
with something that is not a triplet-bsp string is incorrect to start
with, but attempting to address that is not done here.
---

This should fix the issue discovered by David Siddons and Frank Kühndel
described in the "build failed" thread from 2023-07-23 in the
rtems-users mailing list with message-id:
<8e6c2841-ae9e-aacf-de84-e6340d204...@embedded-brains.de>

I have tested this fix when compiling the simple quickstart application
for the sparc-gaisler-rtems5-leon3 and arm-rtems6-xilinx_zynq_zc702
targets, but I have not verified execution of the build results, this is
probably the amount of testing that I will be able to perform at the
moment.

 rtems.py | 14 --
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/rtems.py b/rtems.py
index c65a7d2..a29d281 100644
--- a/rtems.py
+++ b/rtems.py
@@ -859,15 +859,17 @@ def _check_arch_bsps(req, config, path, archs, version):
 
 def _arch_from_arch_bsp(arch_bsp):
 fields = arch_bsp.split('-')
-rtems_field_index = next(i for i, field in enumerate(fields) if 
field.startswith('rtems'))
-return '-'.join(fields[:(rtems_field_index + 1)])
-
+for i, field in enumerate(fields):
+if field.startswith('rtems') and fields[:(i + 1)] is not None:
+return '-'.join(fields[:(i + 1)])
+return None
 
 def _bsp_from_arch_bsp(arch_bsp):
 fields = arch_bsp.split('-')
-rtems_field_index = next(i for i, field in enumerate(fields) if 
field.startswith('rtems'))
-return '-'.join(fields[(rtems_field_index + 1):])
-
+for i, field in enumerate(fields):
+if field.startswith('rtems') and fields[(i + 1):] is not None:
+return '-'.join(fields[(i + 1):])
+return None
 
 def _pkgconfig_path(path):
 return os.path.join(path, 'lib', 'pkgconfig')
-- 
2.30.2

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: ADA, gnat, rtems 6, ubuntu 22LTS

2023-10-05 Thread Frank Kühndel 

Hello Emanuel,

I cannot say anything about your specific issue. I can just provide this 
information:


Our CI/CD builds rtems-tools with ADA on Ubuntu 22.04 for RSB, Git 
commit 35c73203df1e0bc7f0935cfb37ebc6581d8f1103 for aarch64, arm, bfin, 
i386, m68k, mips, moxie, nios2, or1k, powerpc, riskv, sparc, x86_64. The 
other architectures seem to have problems. Moreover, ADA is only build 
but not tested.


The big issue between building with and without ADA comes down to have 
Ubuntu specially setup for the RTEMS Source Builder to being able to 
build ADA. I need these packages:


bzip2
gcc-12
g++-12
gnat-12

And I need the following links (all g** compiler tools must have the 
same version 12 and all must be available without the "-12" postfix):


ln -s gcc /usr/bin/cc

for exe in /usr/bin/gcc*12 /usr/bin/gcov*12 /usr/bin/g++*12; do
   ln -s $exe ${exe%-12}
done

Greetings
Frank

On 10/4/23 19:02, emanuel stiebler wrote:

Subject:
ADA, gnat, rtems 6, ubuntu 22LTS
From:
emanuel stiebler 
Date:
10/4/23, 19:02

To:
"rtems-de...@rtems.org" 


I just tried to compile the tools for rtems6,
and just with "C", everything(?) works.

Trying to add ADA to the tools, it fails, complaining about gnat not 
being installed.

In the logfile:

hecking for objdir... .libs
configure: WARNING: using in-tree isl, disabling version check
configure: error: GNAT is required to build ada
shell cmd failed: /bin/sh -ex 
/AD1/PUB/RTEMS.work/rsb/rtems/build/aarch64-rtems6-gcc-506cb58-newlib-a021448-x86_64-linux-gnu-1/do-build
error: building 
aarch64-rtems6-gcc-506cb58-newlib-a021448-x86_64-linux-gnu-1emu@W531:/AD1/PUB/RTEMS.work/rsb/rtems$



but "gnat" gives me:

DDD@W531:/AD1/PUB/RTEMS.work/rsb/rtems$ gnat
GNAT 12.3.0
Copyright 1996-2022, Free Software Foundation, Inc.

To list Ada build switches use --help-ada

List of available commands

gnat bind   x86_64-linux-gnu-gnatbind-12
gnat chop   x86_64-linux-gnu-gnatchop-12
gnat clean  x86_64-linux-gnu-gnatclean-12
gnat compile    x86_64-linux-gnu-gnatmake-12 -f -u -c
gnat check  x86_64-linux-gnu-gnatcheck-12
gnat elim   x86_64-linux-gnu-gnatelim-12
gnat find   x86_64-linux-gnu-gnatfind-12
gnat krunch x86_64-linux-gnu-gnatkr-12
gnat link   x86_64-linux-gnu-gnatlink-12
gnat list   x86_64-linux-gnu-gnatls-12
gnat make   x86_64-linux-gnu-gnatmake-12
gnat metric x86_64-linux-gnu-gnatmetric-12
gnat name   x86_64-linux-gnu-gnatname-12
gnat preprocess x86_64-linux-gnu-gnatprep-12
gnat pretty x86_64-linux-gnu-gnatpp-12
gnat stack  x86_64-linux-gnu-gnatstack-12
gnat stub   x86_64-linux-gnu-gnatstub-12
gnat test   x86_64-linux-gnu-gnattest-12
gnat xref   x86_64-linux-gnu-gnatxref-12


Report bugs to rep...@adacore.com

What am I missing?
(GIT version of yesterday ...)

Cheers & Thanks
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


--
embedded brains GmbH & Co. KG
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11

Registergericht: Amtsgericht München
Registernummer: HRA 117265
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel