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/30882] sim: m32c/opc2c.c: MinGW: undefined reference to `getline'
Date: Sun, 15 Oct 2023 17:19:09 +0000 [thread overview]
Message-ID: <bug-30882-4717-PGGsyLOYXL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30882-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30882
Mike Frysinger <vapier at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Assignee|unassigned at sourceware dot org |vapier at gentoo dot org
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2023-10-15
--- Comment #2 from Mike Frysinger <vapier at gentoo dot org> ---
the top-level configurey already supports building subdirs for the --build
system. so i posted some patches to leverage that and link them in to our
build-time tools.
https://sourceware.org/pipermail/gdb-patches/2023-October/203256.html
https://sourceware.org/pipermail/gdb-patches/2023-October/203257.html
https://sourceware.org/pipermail/gdb-patches/2023-October/203258.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-15 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 11:27 [Bug build/30882] New: MinGW: undefined reference to `getline' in m32c/opc2c.c orgads at gmail dot com
2023-09-24 11:33 ` [Bug build/30882] " orgads at gmail dot com
2023-10-15 3:18 ` [Bug sim/30882] sim: m32c/opc2c.c: MinGW: undefined reference to `getline' vapier at gentoo dot org
2023-10-15 17:19 ` vapier at gentoo dot org [this message]
2024-03-03 11:25 ` orgads at gmail dot com
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-30882-4717-PGGsyLOYXL@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).