<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 28, 2016 at 5:32 PM, Chris Johns <span dir="ltr"><<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 29/11/2016 09:58, Joel Sherrill wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
On Mon, Nov 28, 2016 at 3:49 PM, Chris Johns <<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a><br></span><span class="gmail-">
<mailto:<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>>> wrote:<br>
<br>
On 27/11/2016 11:36, Joel Sherrill wrote:<br>
<br>
On Nov 26, 2016 6:48 PM, "Chris Johns" <<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a><br>
<mailto:<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>><br></span><span class="gmail-">
<mailto:<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a> <mailto:<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>>>> wrote:<br>
><br>
> On 26/11/16 4:02 am, Joel Sherrill wrote:<br>
> > This has had great support from the gdb developers.<br>
><br>
> Yes the turn around time for this fix was excellent.<br>
><br>
> ><br>
> > Did any of the other targets show an issue?<br>
> ><br>
><br>
> I do not know. I have built sparc tools with the patch. I do<br>
not know if<br>
> it was also broken.<br>
<br>
This was a build error so we need to build all the tools on<br>
FreeBSD to<br>
check.<br>
<br>
<br>
I built 4.12/rtems-all on FreeBSD and the following failed:<br>
<br>
epiphany-rtems4.12-gdb-7.8.1-x<wbr>86_64-freebsd10.3-1<br>
m32c-rtems4.12-gdb-7.9-x86_64-<wbr>freebsd10.3-1<br>
mips-rtems4.12-gcc-6-20161110-<wbr>newlib-2.4.0.20161025-x86_64-f<wbr>reebsd10.3-1<br>
mipstx39-rtems4.12-gdb-7.9-x86<wbr>_64-freebsd10.3-1<br>
<br>
The issues are:<br>
<br>
epiphany-rtems4.12-gdb:<br>
m32c-rtems4.12-gdb-7.9:<br>
mipstx39-rtems4.12-gdb-7.9:<br>
- libiconv issue<br>
<br>
I don't recall this one.<br>
<br>
</span></blockquote>
<br>
I suspect libiconv support needs a path or a library for some versions. The complication is iconv support changed with FreeBSD v10. This means the generic gdb build recipe may need help to be taught how to do this.<span class="gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
mips-rtems4.12-gcc-6-20161110-<wbr>newlib-2.4.0.20161025:<br>
- BSD shell issue in the expansion of the multilibs.<br>
<br>
We have emailed/filed/discussed this before with the GCC folks.<br>
The resolution was to use GNU sed.<br>
</blockquote>
<br></span>
Yes I remember.<span class="gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
They were not willing to<br>
rewrite the t-* fragment to use BSD sed and GNU sed.<br>
</blockquote>
<br></span>
This is an unfortunate situation and it creates a negative feeling towards the gcc project. I would like to know if the cause is the result of a non-standards based feature in the GNU sed.<span class="gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Unless we find a sed expert, this is the solution.<br>
</blockquote>
<br></span>
It is not sed I had the problem with, it was the expected output. It requires knowledge of the expected MIUPS mult-libs. Plus I found the gcc build system with this stuff difficult to debug and see what the issue actually is.</blockquote><div><br></div><div>Ping the GCC Pr and see if Richard Sandiford can at least provide</div><div>example input and output. </div><div><br></div><div><a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62097">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62097</a><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> > I think this got applied to the 7.12 branch and master, right?<br>
><br>
> Sorry, I do not know. I think this patch should be pushed<br>
until a<br>
> release with the fix is available. Ok to push?<br>
<br>
I thought they put it on both but we need the patch so push what is<br>
needed for 7.12.<br>
<br>
<br>
They may have however I am not sure what you are asking.<br>
<br>
RTEMS has to use 7.12 as is with what patches we need. When 7.12.1 is<br>
out, we should jump to that.<br>
</blockquote>
<br></span>
Yes, however it is not clear to me if you are saying wait for that or can this patch be pushed? I do not think I have seen a clear OK to push, I may have missed it.<span class="gmail-HOEnZb"><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div>Push it. :)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-HOEnZb"><font color="#888888">
Chris<br>
</font></span></blockquote></div><br></div></div>