public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/27705] Error cross-compiling binutils-gdb for windows
Date: Tue, 13 Apr 2021 01:42:54 +0000 [thread overview]
Message-ID: <bug-27705-4717-6QIbq4W7sA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27705-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27705
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
If you want to try your hand at fixing the bug, the very
best thing to do would be to convert the callback 'time'
field to be of type 'time_t (*) (host_callback *)' -- removing
the second argument and using the correct return type.
If you don't want the sim, use --disable-sim when configuring
as a quick workaround.
If you do want the sim, but don't want to get too deep in
the weeds, I guess you can rewrite os_time to create a local
time_t and then cast it back; though from what I can tell
just using 'time (NULL)' would work as well, since no caller
seems to use this parameter.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-13 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 9:58 [Bug sim/27705] New: " stepanstepan0000 at gmail dot com
2021-04-13 1:42 ` tromey at sourceware dot org [this message]
2021-04-13 3:37 ` [Bug sim/27705] " vapier at gentoo dot org
2021-04-24 18:44 ` [Bug sim/27705] sim/callback.c fails when time_t is not a long due to passing long* to time() vapier at gentoo dot org
2021-05-15 1:06 ` cvs-commit at gcc dot gnu.org
2021-05-15 1:20 ` vapier at gentoo dot org
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=bug-27705-4717-6QIbq4W7sA@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).