Hi,
Building all ARM BSPs on master today I get ...
checking for arm-rtems5-gcc... (cached) arm-rtems5-gcc
checking whether the C compiler works... no
configure: error: in
`/opt/work/chris/rtems/kernel/bsps/arm/arm-rtems5/c/lpc40xx_ea_ram':
configure: error: C compiler cannot create executables
S
Hi
I don't know enough about spike to know what happened. Just looking through
the logs of
an overnight build/test sweep and noticed this.
===
[331/579] p:312 f:3 u:5 e:0 I:0 B:3 t:0 error: spike.cfg:58:
execute failed: spike --isa=RV32IMAC
./riscv-rtems5/c/rv32imac/testsui
---
bsps/riscv/riscv/console/console-config.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/bsps/riscv/riscv/console/console-config.c
b/bsps/riscv/riscv/console/console-config.c
index 464b4b0e26..5226285272 100644
--- a/bsps/riscv/riscv/console/console-confi
This is to hide the new BSPs from GCC builds when building
all RISC-V BSPs with configure --target=riscv-rtems5
---
.../config/{rv32i_clang.cfg => rv32i_clang.ccfg} | 0
.../{rv32iac_clang.cfg => rv32iac_clang.ccfg} | 0
.../config/{rv32im_clang.cfg => rv32im_clang.ccfg} | 0
.../{rv32im
On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote:
>
>
>
> On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary
> wrote:
>>
>> On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote:
>> >
>> >
>> >
>> > On 28/10/19 9:21 am, Hesham Almatary wrote:
>> > >
>> > >
>> > > On Sun, 27 Oct 2019 at 20:54, Chris Joh