On Sun, Apr 5, 2020, 3:09 PM Hesham Almatary <hesham.almat...@cl.cam.ac.uk> wrote:
> On Sun, 5 Apr 2020 at 21:00, Joel Sherrill <j...@rtems.org> wrote: > > > > > > > > On Sun, Apr 5, 2020 at 2:54 PM Hesham Almatary < > hesham.almat...@cl.cam.ac.uk> wrote: > >> > >> On Sun, 5 Apr 2020 at 20:31, Joel Sherrill <j...@rtems.org> wrote: > >> > > >> > RTEMS is using this hash: 50782bc5cf00bbaa3ac5200009c6a901f7a52905 > >> > RSB is using this hash: 113c65cb56d04c59a0e145f85864fb431419dfa9 > >> > > >> > I can see a couple of fairly obvious odd issues beyond probably > missing > >> > the patches you mention: > >> > > >> > + dtc is older as an RSB recipe by itself than when built with Spike > >> > > >> > + spike doesn't build on FreeBSD > >> > > >> We may pull this patch in RSB to build Spike on FreeBSD > >> https://github.com/CTSRD-CHERI/riscv-isa-sim/pull/7/ > > > > > > Hesham, can you update the Spike RSB to do that? > > > Unfortunately I don't have a FreeBSD box to test on. I can test it on > Linux, but I won't build if it works on FreeBDS or not. > You get the patch ready and I will test it for you. In case you haven't heard me, these test sweeps are running about ~24 hours on a fast machine (8 core Xeon) and ~33 on an early quad-core. If people want specific patches tested on FreeBSD between big runs, I can start doing that. > > And it shouldn't take much time while you are there to bump the dtc > > to the same as in the spike recipe. > > > > Please and thank you. > >> > >> > >> > >> > + GDB build issue with iconv on FreeBSD 12. > >> > > >> > + Did the atsamv issue where it couldn't link all rtems-libbsd tests > get fixed? > >> > > >> > It takes a while to dig through the failures. I trust the failures on > Centos and > >> > Ubuntu to be RTEMS related while the FreeBSD ones tend to be in tools. > >> > And that triggers more not working. > >> > > >> > --joel > >> > > >> > On Sun, Apr 5, 2020 at 2:04 PM Christian Mauderer <o...@c-mauderer.de> > wrote: > >> >> > >> >> Hello Joel, > >> >> > >> >> libbsd on raspberry should work again since yesterday (if you refer > to > >> >> that ticket: https://devel.rtems.org/ticket/3903). > >> >> > >> >> Did your build already include the revert here: > >> >> > https://git.rtems.org/rtems/commit/?id=d582d0e130a463842e27070a2e85ebc1acc7b71f > >> >> > >> >> Sebastian reverted it after Chris said that it broke some builds: > >> >> https://lists.rtems.org/pipermail/devel/2020-April/059014.html > >> >> > >> >> Best regards > >> >> > >> >> Christian > >> >> > >> >> On 05/04/2020 18:28, Joel Sherrill wrote: > >> >> > Hi > >> >> > > >> >> > It will take me some time to go through all the failures reported > on my > >> >> > overnight sweep (which isn't finished everywhere) for Centos 7, > Ubuntu, > >> >> > and FreeBSD. > >> >> > > >> >> > Please try to look at the failure messages at > >> >> > > >> >> > https://lists.rtems.org/pipermail/build/2020-April/date.html > >> >> > > >> >> > And see if you can help identify the various root causes and fix > them. > >> >> > > >> >> > It appears that a number of the BSP bsets do not build to > completion > >> >> > on Centos, many things fail on FreeBSD 12, etc. For example, this > >> >> > for the PC BSP bset on CentOS: > >> >> > > >> >> > https://lists.rtems.org/pipermail/build/2020-April/012862.html > >> >> > > >> >> > The rasperrypi2 bset build failure is well-known and has a ticket. > >> >> > > >> >> > Help is really appreciated triaging and fixing these. > >> >> > > >> >> > --joel > >> >> > > >> >> > _______________________________________________ > >> >> > devel mailing list > >> >> > devel@rtems.org > >> >> > http://lists.rtems.org/mailman/listinfo/devel > >> >> > > >> > > >> > _______________________________________________ > >> > devel mailing list > >> > devel@rtems.org > >> > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel