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: Fri, 22 Oct 2021 15:58:52 +0000 [thread overview]
Message-ID: <bug-28476-4717-XskWVb008d@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 #6 from Mike Frysinger <vapier at gentoo dot org> ---
i build all the sims with:
--enable-targets=all --enable-gdb --enable-sim --host=i686-w64-mingw32
and they're working for me now. you didn't say the exact target you're using
to compile here.
that output looks like it's running on Windows, but i'm not familiar with the
error messages generated. is that a GNU assembler ?
C:\Users\orgads\AppData\Local\Temp\cco9NQ8A.s: Assembler messages:
C:\Users\orgads\AppData\Local\Temp\cco9NQ8A.s:208: Error: value of
0000001000000339 too large for field of 4 bytes at 00000000000000f9
the LPSIZE error messages suggest you're using an out-of-date source tree.
please make sure you have the latest git before trying to build anything.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-22 15:58 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 [this message]
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
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-XskWVb008d@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).