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: Tue, 26 Oct 2021 04:52:06 +0000 [thread overview]
Message-ID: <bug-28476-4717-b7JddeQf7v@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 #11 from Mike Frysinger <vapier at gentoo dot org> ---
not sure why you're changing the config.h path. the search paths should be
such that only the sim one is located.
the sim is cross-compiling for me using current toolchain projects:
cross-i686-w64-mingw32/binutils-2.37_p1
cross-i686-w64-mingw32/gcc-11.2.0
cross-i686-w64-mingw32/mingw64-runtime-8.0.0
feel free to dig into those CPP errors more to see why they're showing up for
you
the getline ones are obvious. we aren't building gnulib for the build system,
only the host, so tools we compile for the build system fail. that said,
getline is in POSIX now, so it sounds like maybe the mingw you're building
against needs fixing (and is worth filing a bug for them).
no idea about the assembler errors. looks like a Windows thing.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-26 4:52 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 [this message]
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
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-b7JddeQf7v@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).