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 out
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
On 10/04/2020 22:38, Hesham Almatary wrote:
Hello Sebastian,
On Fri, 10 Apr 2020 at 20:23, Sebastian Huber
wrote:
On 10/04/2020 12:39, Hesham Almatary wrote:
Don't default to gcc if the compiler can't be found
All options should have a default. I should be possible to build a BSP
just wit
Hello Sebastian,
On Fri, 10 Apr 2020 at 20:23, Sebastian Huber
wrote:
>
> On 10/04/2020 12:39, Hesham Almatary wrote:
>
> > Don't default to gcc if the compiler can't be found
>
> All options should have a default. I should be possible to build a BSP
> just with:
>
> [arch/bsp]
>
This patch doesn
On 10/04/2020 12:39, Hesham Almatary wrote:
Don't default to gcc if the compiler can't be found
All options should have a default. I should be possible to build a BSP
just with:
[arch/bsp]
___
devel mailing list
devel@rtems.org
http://lists.rtems
Don't default to gcc if the compiler can't be found
---
wscript | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/wscript b/wscript
index b135da74be..c0a3fd31e8 100755
--- a/wscript
+++ b/wscript
@@ -1232,7 +1232,8 @@ def get_compiler(conf, cp, variant):
value = no_uni