public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/28476] MinGW build for all targets is broken
Date: Mon, 01 Nov 2021 03:14:05 +0000 [thread overview]
Message-ID: <bug-28476-4717-dNKUvPcTCQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28476-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28476
--- Comment #20 from Mike Frysinger <vapier at gentoo dot org> ---
(In reply to Orgad Shaneh from comment #18)
> Regarding getline, shouldn't it be provided by gnulib?
we currently only build gnulib for the --host system, not --build. so we are
providing gnulib too --host, but these are --build tools which don't help.
> MinGW is not POSIX.
i'll note that MinGW literally means "Minimalist GNU for Windows". getline was
a GNU extension that made it into POSIX. the logical thing really is for MinGW
to support the latest POSIX and include GNU extensions.
but i don't know when upstream MinGW is going to get around to that, and we try
to build GNU sim on more than POSIX systems. would be nice if we figured out
how to build & use gnulib for --build too
> I attached a verbose assembly of the file. These are the errors for this
> file:
> func.s:2241: Error: value of 0000001000001e8d too large for field of 4 bytes
> at 000000000000134d
i'm thinking this is a bug in either gcc or the assembler, but prob gcc. so
this should get reported to the gcc folks.
> https://sourceware.org/pipermail/gdb-patches/2021-October/182836.html
that touches top-level files which needs someone to review that. i suspect the
answer isn't to force line encodings, so you'll prob want to file a dedicated
bug if the gas manual is failing to build under Windows.
for the sim parts, i pushed a fix for igen instead:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f0982318065617e92c28e23ee382981c2a898ca2
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-01 3:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 19:20 [Bug gdb/28476] New: " orgads at gmail dot com
2021-10-19 19:29 ` [Bug gdb/28476] " orgads at gmail dot com
2021-10-19 19:30 ` orgads at gmail dot com
2021-10-19 19:37 ` orgads at gmail dot com
2021-10-20 4:30 ` linly2999 at gmail dot com
2021-10-22 15:16 ` [Bug sim/28476] " tromey at sourceware dot org
2021-10-22 15:58 ` vapier at gentoo dot org
2021-10-23 18:45 ` orgads at gmail dot com
2021-10-23 18:49 ` orgads at gmail dot com
2021-10-23 21:23 ` vapier at gentoo dot org
2021-10-24 22:03 ` orgads at gmail dot com
2021-10-26 4:52 ` vapier at gentoo dot org
2021-10-26 14:23 ` orgads at gmail dot com
2021-10-26 14:24 ` orgads at gmail dot com
2021-10-26 19:18 ` vapier at gentoo dot org
2021-10-27 6:30 ` orgads at gmail dot com
2021-10-27 6:33 ` orgads at gmail dot com
2021-10-31 16:56 ` vapier at gentoo dot org
2021-10-31 19:00 ` orgads at gmail dot com
2021-10-31 19:49 ` orgads at gmail dot com
2021-11-01 3:14 ` vapier at gentoo dot org [this message]
2021-11-01 5:09 ` vapier at gentoo dot org
2022-05-13 6:18 ` orgads at gmail dot com
2022-05-13 10:52 ` pedro at palves dot net
2022-05-14 1:03 ` vapier at gentoo dot org
2022-05-14 18:14 ` orgads at gmail dot com
2023-09-24 11:34 ` orgads at gmail dot com
2024-03-21 16:49 ` cvs-commit at gcc dot gnu.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-28476-4717-dNKUvPcTCQ@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).