public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@crelg.com, gdb-patches@sourceware.org
Subject: Re: Enabled TUI mode on MSYS2
Date: Sun, 18 Sep 2016 23:40:00 -0000	[thread overview]
Message-ID: <1c5a8e3b-5e6b-999e-e62e-a4511e8d1f50@redhat.com> (raw)
In-Reply-To: <83h99e50h5.fsf@gnu.org>

On 09/17/2016 10:39 AM, Eli Zaretskii wrote:

> I get messages about my commit broke the build.  But I don't
> understand the nature of the breakage: all of the errors complain
> about min and max in the 'gdb' directory, whereas I didn't change
> anything in that directory, and didn't introduce any calls or
> definitions of min or max.

Sounds like you're building for 32-bit.  My std::min/std::max
broke those, sorry about that.  I don't know why the buildbot
is putting the blame on your patch.  Anyway, should be fixed now.
Let me know if you still see build problems.

> 
> Help will be appreciated.
> 
> Sorry for the mess.
> 

Thanks,
Pedro Alves

  reply	other threads:[~2016-09-18 23:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 21:21 Giah de Barag
2016-09-14  2:42 ` Eli Zaretskii
2016-09-14  6:32   ` Giah de Barag
2016-09-14 17:22     ` Eli Zaretskii
2016-09-14 17:33       ` Pedro Alves
2016-09-14 18:33       ` Giah de Barag
2016-09-14 18:36         ` Pedro Alves
2016-09-14 18:59           ` Eli Zaretskii
2016-09-14 19:04             ` Pedro Alves
2016-09-17  8:53               ` Eli Zaretskii
2016-09-17  9:39                 ` Eli Zaretskii
2016-09-18 23:40                   ` Pedro Alves [this message]
2016-09-20 22:45                   ` Sergio Durigan Junior

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=1c5a8e3b-5e6b-999e-e62e-a4511e8d1f50@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@crelg.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).