<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div>On 6 May 2018, at 7:04 am, Vijay Kumar Banerjee <<a href="mailto:vijaykumar9597@gmail.com">vijaykumar9597@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On 6 May 2018 at 02:25, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On 5 May 2018 at 21:12, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
> On 6 May 2018, at 2:44 am, Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>> wrote:<br>
> <br>
> Looks similar to Cillian's failure. Chris will have to show me where libdwarf comes from. It needs to be supplied with RTEMS tools for consistency.<br>
<br>
</span>You need to apply the patches against master. I added libdwarf to master the other day. <br></blockquote><div><br></div></span><div>That is applied to current master. I can see that libdwarf patch in the log but it still has that </div></div></div></div></blockquote><div>same here.</div></div></div></div></div></blockquote><div><br></div><div>Thank you for the fast response. </div><div><br></div><div>Do you think a host version is being picked up before the rtemtoolkit one?</div><div><br></div><div>Could you please check covoar’s wscript has the libdwarf path added?</div><div><br></div><div>Also check waf with -v. </div><div><br></div><div>Thanks </div><div>Chris </div></body></html>