On Wed, Aug 14, 2019, 6:02 PM Chris Johns <chr...@rtems.org> wrote: > On 15/8/19 8:50 am, Joel Sherrill wrote: > > On Wed, Aug 14, 2019 at 5:27 PM Chris Johns <chr...@rtems.org> wrote: > >> > >> On 15/8/19 8:08 am, Joel Sherrill wrote: > >>> qemu-couverture.bset explicitly has 1.4.1. > >> > >> OK. > >> > >>> qemu.bset doesn't list dtc at all. No idea why not. > >> > >> Because you cannot build dtc on MinGW and I doubt you ever will be able > to. Here > >> the MSYS2 package is used. I cannot remember the specifics. > >> > >>> But qemu-git-1.cfg has a dtc submodule of qemu pulled out of git so I > >>> guess qemu.bset is implicitly getting that. > >> > >> Yes, qemu's release cycle did not carry changes we needed. > >> > >>> Clear as mud to me. > >> > >> Be careful here because it a rather deep hole and time consuming to get > all this > >> to work on all hosts. The qemu.bset did build on all hosts we support > at one > >> point in time. > > > > Should I punt and use the native provided dtc? Or try to build it by > hand as a > > singleton using the RSB? > > > > I think updating to 1.4.1 vs 1.2 is OK but am happy to drop it from > > the qemu set. > > Yeap. > > > But we can defer this and I will try dtc 1.2 as an RSB singleton, then > host DTC. > > It is needed by spike. > > I do not know as I cannot remember the specific now and things may have > changed. > > Maybe add it and then try and see what breaks? >
I'll take the baby step of building it from the rsb manually until we get all the testing hosts online. > > Chris >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
