Problem with clang support in waf

Hello, I made some preparations to support also clang in the new build system. You can configure the compiler per BSP variant, e.g. [riscv/rv32imac] COMPILER = clang # Flags passed to the library archiver ARFLAGS = crD # Warning flags passed to the C compiler CC_WARNING_FLAGS =

Re: sparc-rtems-gdb doesn't recognize target "sim"

On Wed, Nov 13, 2019 at 12:39 AM Shubham Bhagat wrote: > Hello everyone, > I've been trying to run the hello world example in source tree > to get > started with sparc/erc32 but after building all that is required ( followed >

Re: *.tcfg specification?

On 13/11/2019 01:39, Chris Johns wrote: > Ok, it seems a test program has exactly one state for a given BSP. Yes, this is driven by the ABI, hardware profile and similar constraints. This is generally the case but we have a few BSPs where the same executable runs on real hardware

Re: [PATCH] eng: Add build system chapter

On 13/11/19 5:14 pm, Sebastian Huber wrote: > We already have a recursive substitution built in through the DAG. Sure, and this is only a suggestion. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] eng: Add build system chapter

On 12/11/2019 22:43, Chris Johns wrote: The variables used for the substitution are the configuration set environment variables. I intentionally didn't add a recursive substitution since you should specify the variable definitions in a proper order. And if there are competing orders? It all

Re: *.tcfg specification?

On 13/11/19 10:09 am, Joel Sherrill wrote: > On Tue, Nov 12, 2019 at 4:42 PM Chris Johns > wrote: > On 13/11/19 1:30 am, Sebastian Huber wrote: > > Hello Chris, > > > > thanks for your comments. I converted now all tests except the Ada > tests, > >

Re: *.tcfg specification?

On Tue, Nov 12, 2019 at 4:42 PM Chris Johns wrote: > On 13/11/19 1:30 am, Sebastian Huber wrote: > > Hello Chris, > > > > thanks for your comments. I converted now all tests except the Ada > tests, > > Nice. > > > tests which use the pax tool, > > This might help ... > >

Re: *.tcfg specification?

On 13/11/19 1:30 am, Sebastian Huber wrote: > Hello Chris, > > thanks for your comments. I converted now all tests except the Ada tests, Nice. > tests which use the pax tool, This might help ... https://git.rtems.org/rtems_waf/tree/rootfs.py > and the dl* tests. Plus this ...

Re: [PATCH] eng: Add build system chapter

On 12/11/19 5:05 pm, Sebastian Huber wrote: > On 11/11/2019 23:29, Chris Johns wrote: >> On 11/11/19 8:45 pm, Sebastian Huber wrote: >>> On 08/11/2019 23:48, Chris Johns wrote:[...] 3. Is the ${} expansion something you have implemented? It is a nice feature. >>> [...] >>> >>> With

sparc-rtems-gdb doesn't recognize target "sim"

Hello everyone,I've been trying to run the hello world example in source tree to get started with sparc/erc32 but after building all that is required ( followed POSIX Compliance (Getting started challenge for RTEMS beginners)). Ifollowed all the commands. But, when gdb starts and I set "tar

Re: [PATCH] bsps/riscv: HTIF - Use 32-bit HTIF syscalls on RV32

On 12/11/2019 14:22, Hesham Almatary wrote: HTIF devices are not supported on RV32, so proxy a write system call This syncs HTIF Console with riscv-pk (proxy kernel) to use 32-bit HTIF syscalls on RV32 instead of 64-bit commands that are not atomic. Looks good. -- Sebastian Huber, embedded

Re: *.tcfg specification?

Hello Chris, thanks for your comments. I converted now all tests except the Ada tests, tests which use the pax tool, and the dl* tests. For an approach to address the test states please see below. On 11/11/2019 23:25, Chris Johns wrote: On 11/11/19 7:13 pm, Sebastian Huber wrote: what is

[PATCH] bsps/riscv: HTIF - Use 32-bit HTIF syscalls on RV32

HTIF devices are not supported on RV32, so proxy a write system call This syncs HTIF Console with riscv-pk (proxy kernel) to use 32-bit HTIF syscalls on RV32 instead of 64-bit commands that are not atomic. --- bsps/riscv/riscv/console/htif.c | 65 ++--- 1 file

Re: [rtems commit] termios: Add Capability to Generate SIGINTR and SIGQUIT

On 09/10/2019 21:34, Joel Sherrill wrote: Module:rtems Branch:master Commit:667501a314ba75f80f1c13c6b43dd35d0a00efd1 Changeset: http://git.rtems.org/rtems/commit/?id=667501a314ba75f80f1c13c6b43dd35d0a00efd1 Author:Joel Sherrill Date: Wed Oct 2 16:49:00 2019 -0500