<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 9, 2021 at 2:34 PM Joel Sherrill <<a href="mailto:joel@rtems.org">joel@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 9, 2021 at 1:28 PM Ayushman Mishra <<a href="mailto:ayushvidushi01@gmail.com" target="_blank">ayushvidushi01@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ayusman Mishra<br>
1. I was going through ticket #4145<br>
(<a href="https://devel.rtems.org/ticket/4145" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/4145</a>) and tried building bsp on rtems6<br>
and rtems5 both using rsb<br>
(<a href="https://docs.rtems.org/branches/master/user/start/bsp-build.html#rsb-bsp-build" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/start/bsp-build.html#rsb-bsp-build</a>)<br>
but got Build FAILED (it says pax is missing (configure: error: pax is<br>
missing.), I have attached full error report txt file). However I did<br>
build bsp erc32 and pc386 using rsb on rtems5 (first .bootstrap -c<br>
sb-bootstrap then used configure file<br>
($HOME/development/rtems/rtems-5/configure --target=i386-rtems5<br>
--enable-rtemsbsp=pc386 )) on rtems6 there is no sb-bootstrap file or<br>
configure file present/made.<br>
I wanted to know is there anyway of using RSB on rtems6.<br>
Also while building different bsp toolsets for rtems (erc32/pc386) I<br>
used rtems on 2 different directories , Is there any way of building<br>
different BSPs on same rtems?<br>
<br>
2. I went through list of open projects and found projects related to<br>
testing and development of ecosystem quite interesting,<br>
#3710 <a href="https://devel.rtems.org/ticket/3710" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3710</a></blockquote><div><br></div><div>I recently added Automated Coverity runs. We haven't figured out how to</div><div>scrape the coverity website and turn it into open information. I have exported</div><div>the data they have but it isn't enough to be actionable. If you have some </div><div>creative ideas here, it would be great.</div><div><br></div><div>Coverity is being run once a day if needed so that side of automating is done.</div><div> </div></div></div></blockquote><div><br></div><div>We have a modeling file. It's not clear to me if we can/should add to it to further reduce any false positives. Improving just the modeling file is not really a GSoC-worthy project, although it could be in scope for a broader Coverity-related project, perhaps one that creates a tool to help port Coverity defects from Scan into Trac tickets.</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"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
#3860 <a href="https://devel.rtems.org/ticket/3860" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3860</a></blockquote><div><br></div><div>You should ask about Code Style Checking in thread by itself. Sebastian</div><div>has made progress with one formatter and there needs to be an evaluation</div><div>of how much source code can be run through that reformatter unchanged.</div><div>If it changes anything, is this an adjustment to match our style or something</div><div>we want to accept as a necessary evil of using the formatter.</div><div><br></div><div>When we have a combination or either accepting their format changes and</div><div>ideal configuration settings, carefully working through the source owned</div><div>by the RTEMS Project is the next step.</div><div><br></div><div>And then figuring out how to make it a part of the development process</div><div>and patch review.</div><div><br></div><div>This should have a lot of work and have a good impact on the project.</div><div> </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"><br>
#3892 <a href="https://devel.rtems.org/ticket/3892" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3892</a></blockquote><div><br></div><div>I am not the Python expert to comment on this. I think there has been</div><div>acceptance that some code needs to be Python2 and some can be </div><div>Python3. I think we may have agreed on Python style (to some extent) </div><div>so the previous style project has similar work here.</div><div><br></div><div>But pytest support is an unknown to me.</div><div><br></div><div>This would be good one to start a new thread with so the Python</div><div>experts from RTEMS speak up. </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"><br>
I would be very grateful to know if any of the above projects is open<br>
for participation and if yes then work done/needed to be done in it.<br></blockquote><div><br></div><div>There is probably more work in the latter two. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div></div>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div></div>