public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mitza at objectcomputing dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/26068] MinGW build failed due to ws2_32 dependency Date: Fri, 02 Dec 2022 18:37:53 +0000 [thread overview] Message-ID: <bug-26068-4717-Ax28W4lKfV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26068-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26068 --- Comment #11 from Adam Mitz <mitza at objectcomputing dot com> --- I didn't come back to it after https://sourceware.org/pipermail/gdb-patches/2020-June/169376.html The project I was potentially going to use a from-source build of GDB on ended up going in a different direction. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-12-02 18:37 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 16:54 [Bug build/26068] New: " mitza at objectcomputing dot com 2020-06-02 17:20 ` [Bug build/26068] " mitza at objectcomputing dot com 2020-06-02 22:41 ` simark at simark dot ca 2020-06-03 15:42 ` mitza at objectcomputing dot com 2020-06-03 19:20 ` simark at simark dot ca 2020-06-03 19:24 ` cbiesinger at google dot com 2020-06-04 20:45 ` ssbssa at sourceware dot org 2020-06-04 20:46 ` cbiesinger at google dot com 2020-06-04 22:36 ` mitza at objectcomputing dot com 2020-06-04 22:45 ` ssbssa at sourceware dot org 2021-06-11 21:00 ` alfedotov at gmail dot com 2022-12-02 18:32 ` tromey at sourceware dot org 2022-12-02 18:33 ` tromey at sourceware dot org 2022-12-02 18:37 ` mitza at objectcomputing dot com [this message]
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-26068-4717-Ax28W4lKfV@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).