From: Jeff Law <law@redhat.com>
To: newlib@sourceware.org
Subject: Fwd: Recent newlib/cygwin change breaking cris targets
Date: Mon, 19 Aug 2019 15:09:00 -0000 [thread overview]
Message-ID: <0bdf5c38-fe3b-b657-df45-8f0b73e901c7@redhat.com> (raw)
In-Reply-To: <20190817081837.GY11632@calimero.vinschen.de>
-------- Forwarded Message --------
Subject: Re: Recent newlib/cygwin change breaking cris targets
Date: Sat, 17 Aug 2019 10:18:37 +0200
From: Corinna Vinschen <vinschen@redhat.com>
To: Jeff Law <law@redhat.com>
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
next parent reply other threads:[~2019-08-19 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190817081837.GY11632@calimero.vinschen.de>
2019-08-19 15:09 ` Jeff Law [this message]
2019-08-19 22:05 ` Jeff Johnston
2019-08-19 22:23 ` Jeff Law
2019-08-20 15:26 ` Jeff Law
2019-08-20 16:16 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0bdf5c38-fe3b-b657-df45-8f0b73e901c7@redhat.com \
--to=law@redhat.com \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).