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 19:18:56 +0000 [thread overview] Message-ID: <bug-28476-4717-TYdUYKBfO6@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 #14 from Mike Frysinger <vapier at gentoo dot org> --- the log unfortunately is not sufficient to dive into because the compiler isn't providing enough diagnostics. focus on one failure at a time. for example, go into sim/mips/ and run `make V=1`. look at the first failure (hopefully sim-utils.c), then take the compiler invocation and change the -c to -E -dD, and run it by hand. it should hopefully produce a better error message. if that works, look at the .o file it created (which you should rename to .i) and try to see what it is complaining about. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-26 19:18 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 [this message] 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-TYdUYKBfO6@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: linkBe 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).