Re: Recent newlib/cygwin change breaking cris targets

I have posted a fix that should solve the problem.  I don't have a cris-elf
toolchain to test so if there are any issues,
please let me know.

-- Jeff J.

On Mon, Aug 19, 2019 at 11:09 AM Jeff Law <[email protected]> wrote:

>
>
>
> -------- Forwarded Message --------
> Subject: Re: Recent newlib/cygwin change breaking cris targets
> Date: Sat, 17 Aug 2019 10:18:37 +0200
> From: Corinna Vinschen <[email protected]>
> To: Jeff Law <[email protected]>
>
> On Aug 16 12:35, Jeff Law wrote:
> > Your most recent change to newlib-cygwin is breaking the cris-elf and
> > crisv32-elf targets:
> >
> >
> >
> > In file included from fstat.c:7:
> > fstat.c: In function ‘_fstat’:
> > fstat.c:29:22: error: ‘struct new_stat’ has no member named ‘st_atim’;
> > did you mean ‘st_atime’?
> >    29 |   buf->st_atime = ks.st_atime;
> >       |                      ^~~~~~~~
> > fstat.c:30:22: error: ‘struct new_stat’ has no member named ‘st_mtim’;
> > did you mean ‘st_mtime’?
> >    30 |   buf->st_mtime = ks.st_mtime;
> >       |                      ^~~~~~~~
> > fstat.c:31:22: error: ‘struct new_stat’ has no member named ‘st_ctim’;
> > did you mean ‘st_ctime’?
> >    31 |   buf->st_ctime = ks.st_ctime;
> >       |                      ^~~~~~~~
> >
> > I think you need to update libgloss/cris/gensyscalls.
>
> Can you please send this to the newlib ML, ideally with patch?
> My patch was the result of a discussion starting at
>
> https://sourceware.org/ml/newlib/2019/msg00479.html
>
>
> Thanks,
> Corinna
>