<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Sep 6, 2018 at 9:07 PM Chris Johns <<a href="mailto:chrisj@rtems.org">chrisj@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 6/9/18 9:00 am, Joel Sherrill wrote:<br>
> <a href="https://lists.rtems.org/pipermail/build/2018-September/000997.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/build/2018-September/000997.html</a> still has<br>
> epiphany<br>
> failures. Not sure what else is going on. Do you see the pattern?<br>
<br>
The 'debug' build is not adding '--disable-networking' as the BSP builder is not<br>
tracking defaults or more specifically enabled by default. The SMP works because<br>
the default is disabled while networking has a default of enabled.<br></blockquote><div><br></div><div>Yes. That's clearly the problem. Any ideas on how to address this? I can always</div><div>force networking off for epiphany in the cpukit. We were talking about that anyway.</div><div>Would it be better if exclude implied --disable?</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Chris<br>
</blockquote></div></div>