public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Christian Biesinger <cbiesinger@google.com>,
	Tom Tromey <tromey@adacore.com>,
	simon.marchi@polymtl.ca, gdb-patches@sourceware.org
Subject: Re: Building today's snapshot of GDB with MinGW
Date: Wed, 1 Jul 2020 12:25:41 -0700	[thread overview]
Message-ID: <20200701192541.GC5340@adacore.com> (raw)
In-Reply-To: <83wo3ozlvn.fsf@gnu.org>

Hi Eli,

> > So reading https://sourceware.org/bugzilla/show_bug.cgi?id=25155, Nick
> > mentioned an RFC patch, but I can't tell if that landed.
> 
> Joel, should I install the same libctf patches we had in
> gdb-9.1-branch in the current master?  Or would you like to talk to
> the upstream maintainer first?

Would you mind reaching out to Nick and see what he says? From memory,
what he said was that he had a patch that did away with using errno
values, and that the only blocking point was setting up an environment
to be able to reproduce. I felt back then that this was admirable for
him to try to achieve that, but on the other hand, I was quite concerned
that he was setting the bar to high for himself, and that this would
eventually lead to this being dropped on the floor. That why I offered
"our" (I mean, "your" ;-)) help to validate his patch. Actually, even
if you didn't have the cycles to test it, I think that testing this
kind of patch on his usual architectures would have been sufficient.
So let's just ask him what he prefers, knowing that we need a solution
soon, and that we're happy with using the same hack as on the
gdb-9-branch if that reduces the pressure on his end.

I can join in the discussion if that helps as well.

-- 
Joel

  parent reply	other threads:[~2020-07-01 19:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 18:27 Eli Zaretskii
2020-06-29 20:36 ` Christian Biesinger
2020-06-30 14:09   ` Eli Zaretskii
2020-06-30 22:24     ` Simon Marchi
2020-07-01 15:09       ` Eli Zaretskii
2020-07-02 13:50         ` Eli Zaretskii
2020-07-02 14:25           ` Simon Marchi
2020-07-02 14:30             ` Simon Marchi
2020-07-02 17:47               ` Eli Zaretskii
2020-07-02 14:40             ` Pedro Alves
2020-07-02 17:46               ` Eli Zaretskii
2020-07-02 18:21                 ` Pedro Alves
2020-07-02 18:33                   ` Eli Zaretskii
2020-07-02 18:34                     ` Pedro Alves
2020-07-01 15:20       ` Eli Zaretskii
2020-07-01 19:25         ` Christian Biesinger
2020-07-02  2:29           ` Eli Zaretskii
2020-07-02 10:18             ` Hannes Domani
2020-07-02 13:20               ` Eli Zaretskii
2020-07-06 10:39                 ` Hannes Domani
2020-07-06 16:35                   ` Eli Zaretskii
2020-07-01 19:25     ` Joel Brobecker [this message]
2020-07-02 13:46       ` Eli Zaretskii
2020-06-30 16:18 ` Eli Zaretskii
2020-06-30 18:21   ` Christian Biesinger
2020-06-30 18:28     ` Eli Zaretskii
2020-07-01 19:29   ` Joel Brobecker
2020-07-02  2:31     ` Eli Zaretskii
2020-07-01 19:30   ` Joel Brobecker
2020-07-02 13:39     ` Eli Zaretskii
2020-07-03 15:25       ` Joel Brobecker
2020-07-27  9:49         ` Tom de Vries
2020-07-27 10:05           ` Tom de Vries
2020-07-27 10:26             ` Tom de Vries
2020-07-27 11:48               ` [committed][gdb/build] Fix typo sys/sockets.h -> sys/socket.h Tom de Vries
2020-07-27 12:51                 ` Joel Brobecker
2020-07-27 14:18               ` Building today's snapshot of GDB with MinGW Eli Zaretskii
2020-07-02 14:12 ` Eli Zaretskii
2020-07-03 15:08   ` Eli Zaretskii

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=20200701192541.GC5340@adacore.com \
    --to=brobecker@adacore.com \
    --cc=cbiesinger@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tromey@adacore.com \
    /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).