<html>

  <head>

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

  </head>

  <body>

    <p>On 10/04/2020 22:38, Hesham Almatary wrote:<br>

    </p>

    <blockquote type="cite"

cite="mid:CA+wsVCCPJb6C_ehbGxMSBcvbHyvHK-wjxYmnmC1nFz5c9TVkYQ@mail.gmail.com">

      <div class="moz-text-plain" wrap="true" graphical-quote="true"

        style="font-family: -moz-fixed; font-size: 12px;"

        lang="x-unicode">

        <pre class="moz-quote-pre" wrap="">Hello Sebastian,

On Fri, 10 Apr 2020 at 20:23, Sebastian Huber

<a class="moz-txt-link-rfc2396E" href="mailto:sebastian.huber@embedded-brains.de" moz-do-not-send="true"><sebastian.huber@embedded-brains.de></a> wrote:

</pre>

        <blockquote type="cite" style="color: #000000;">

          <pre class="moz-quote-pre" wrap="">On 10/04/2020 12:39, Hesham Almatary wrote:

</pre>

          <blockquote type="cite" style="color: #000000;">

            <pre class="moz-quote-pre" wrap="">Don't default to gcc if the compiler can't be found

</pre>

          </blockquote>

          <pre class="moz-quote-pre" wrap="">All options should have a default. I should be possible to build a BSP

just with:

[arch/bsp]

</pre>

        </blockquote>

        <pre class="moz-quote-pre" wrap="">This patch doesn't change that behaviour. You can still build a BSP

without providing --rtems-compiler at all and it will default to GCC.

However, this patch addresses the case when you provide an

"--rtems-compiler=blah", where "blah" can't be found nor supported.

For example, without this patch, if I pass "--rtems-compiler=clang"

and it's not supported/found, it will fallback default to GCC silently

without giving any errors. I don't think that's a desirable behaviour.</pre>

      </div>

    </blockquote>

    Could you give me an example command line which shows the undesired

    behaviour?

  </body>

</html>