OK to push?

On Tue, 29 Oct 2019 at 09:25, Hesham Almatary
<hesham.almat...@cl.cam.ac.uk> wrote:
>
> On Mon, 28 Oct 2019 at 23:15, Joel Sherrill <j...@rtems.org> wrote:
> >
> >
> >
> > On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary 
> > <hesham.almat...@cl.cam.ac.uk> wrote:
> >>
> >> On Mon, 28 Oct 2019 at 04:01, Chris Johns <chr...@rtems.org> wrote:
> >> >
> >> >
> >> >
> >> > On 28/10/19 9:21 am, Hesham Almatary wrote:
> >> > >
> >> > >
> >> > > On Sun, 27 Oct 2019 at 20:54, Chris Johns <chr...@rtems.org
> >> > > <mailto:chr...@rtems.org>> wrote:
> >> > >
> >> > >     On 27/10/19 9:37 pm, Hesham Almatary wrote:
> >> > >     > Yeah fesvr is now part of Spike in-tree. I didn't like it had to 
> >> > > be
> >> > >     > built separately either [1].
> >> > >     >
> >> > >     > Joel, AFAIR, dtc was always needed.
> >> > >
> >> > >     Please have the package build FDT if it is needed. Do no rely on 
> >> > > it being
> >> > >     installed as some hosts do not have a package to install.
> >> > >
> >> > > I think Joel has already added it
> >> > > https://github.com/RTEMS/rtems-source-builder/blob/master/bare/config/devel/spike.bset#L7
> >> > >
> >> >
> >> > Thanks.
> >> >
> >> > The config file has some issues. I am fixing the %hash issues. Is the 
> >> > patch
> >> > still needed if the version used has the fix?
> >> >
> >> The version that has the fix is a recent one, and it has fesvr in its
> >> source tree, hence, there's no separate fesvr any more. The patch will
> >> still be needed to get rid of the separate fesvr build for this recent
> >> Spike revision.
> >
> >
> > If you are bumping to a version which doesn't need my patch, great!
> >
> Yes, that's the point of the patch along with removing fesvr build.
>
> > Is this all pushed now?
> >
> Not yet, waiting for approval.
>
> >>
> >> > Chris
> >> > _______________________________________________
> >> > 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

Reply via email to