[PATCH 1/9] [waf] Fatal error if the compiler can't be found

Sebastian Huber sebastian.huber at embedded-brains.de
Sat Apr 11 13:42:57 UTC 2020


On 10/04/2020 23:08, Hesham Almatary wrote:

> I believe my other patch (that outputs COMPILER to config.ini) has
> hidden this issue. I was getting it when I specify
> --rtems-compiler=clang as in
>
>> ./waf bsp_defaults --rtems-bsps=rv64imafdc_medany --rtems-compiler=clang > config.ini
> That didn't output COMPILER in config.ini. So during ./waf configure
> the following line:
>> value = cp.get(conf.variant, "COMPILER")
> triggered an exception, and silently fall back to "gcc", and I didn't
> know what went wrong. I don't think it might happen again now with my
> other patch, but if any of those lines triggered another exception for
> whatever reason, it will fall back to GCC.
Ok, good. The missing COMPILER in ./waf bsp_defaults was clearly a bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200411/91723660/attachment.html>


More information about the devel mailing list