public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29817] x86_64-w64-mingw32 target does not install gdb any more
Date: Sat, 10 Dec 2022 02:11:57 +0000 [thread overview]
Message-ID: <bug-29817-4717-dWdXi9qff1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29817-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29817
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to cqwrteur from comment #3)
> (In reply to Tom Tromey from comment #2)
> > Waiting for response.
>
> x86_64-w64-mingw32 target
>
> I find that even cross toolchain no longer installs x86_64-w64-mingw32-gdb;
> even gdb is built. However, They are not installed.
We need more details to understand what's wrong.
Like, what did you try? How did you configure / make / etc?
What did actually happen?
FWIW this works fine for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-10 2:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 19:43 [Bug build/29817] New: x86_64-w64-mingw32 host does not build " euloanty at live dot com
2022-11-21 19:43 ` [Bug build/29817] " euloanty at live dot com
2022-11-21 21:46 ` simark at simark dot ca
2022-11-22 17:42 ` tromey at sourceware dot org
2022-12-01 21:25 ` tromey at sourceware dot org
2022-12-09 4:01 ` euloanty at live dot com
2022-12-09 4:01 ` [Bug build/29817] x86_64-w64-mingw32 target does not install " euloanty at live dot com
2022-12-10 2:11 ` tromey at sourceware dot org [this message]
2022-12-10 3:56 ` euloanty at live dot com
2023-01-29 3:47 ` euloanty at live dot com
2023-01-29 3:52 ` euloanty at live dot com
2023-01-29 12:57 ` ssbssa at sourceware dot org
2023-01-31 21:01 ` euloanty at live 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-29817-4717-dWdXi9qff1@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).