Hi Sebastian, The *_clang ones aren't expected to be compiled by GCC (and the native *.cfg won't compile with clang). Is there a reason they should be?
On Mon, 28 Oct 2019 at 07:42, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > > Hello, > > when you build the new clang variants with GCC you get: > > gmake[3]: Leaving directory > '/build/git-build/b-all-riscv-5/riscv-rtems5/c/rv32i_clang' > checking for RTEMS_CPU_MODEL... > checking for RTEMS_BSP_FAMILY... riscv > checking for CPU_CFLAGS... (cached) -march=rv32i -mabi=ilp32 -target > riscv32-unknown-rtems6 --sysroot= > checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g -ffunction-sections > -fdata-sections > checking for style of include used by gmake... GNU > checking for riscv-rtems5-gcc... riscv-rtems5-gcc > checking for riscv-rtems5-gcc... (cached) riscv-rtems5-gcc > checking whether the C compiler works... no > configure: error: in > `/build/git-build/b-all-riscv-5/riscv-rtems5/c/rv32i_clang': > configure: error: C compiler cannot create executables > See `config.log' for more details > > Would it be possible to avoid the *_clang.cfg variants and use some > logic on configure.ac to adjust the flags? > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > _______________________________________________ > 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