Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GDB <gdb-patches@sourceware.org>
Subject: Re: Oh dear. I regret to inform you that commit 'ELF: Check ELF_COMMON_DEF_P for common symbols' might be unfortunate
Date: Fri, 07 Apr 2017 15:03:00 -0000	[thread overview]
Message-ID: <CAMe9rOoypJM6go1KhrOcdBdf7=XtZShoo3t7xKh2vT0ODTdbpg@mail.gmail.com> (raw)
In-Reply-To: <E1cwVGv-0000oa-E4@kwanyin.sergiodj.net>

On Fri, Apr 7, 2017 at 7:53 AM,  <gdb-buildbot@sergiodj.net> wrote:
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
>         ELF: Check ELF_COMMON_DEF_P for common symbols
>         8170f7693bc0a9442c0aa280197925db92d48ca6
>
> might have made GDB unwell.  Since I am just your Butler BuildBot,
> I kindly ask that a human superior officer double-check this.
>
> Please note that if you are reading this message on gdb-patches, there might
> be other builders broken.
>
> You can find more details about the unfortunate breakage below.
>
> Cheers,
>
> Your GDB BuildBot.
>

Could someone please fix this?  The problem is

../../binutils-gdb/opcodes/wasm32-dis.c:408:34: error: ‘DECIMAL_DIG’
undeclared (first use in this function)
           prin (stream, " %.*g", DECIMAL_DIG, fconstant);
                                  ^
../../binutils-gdb/opcodes/wasm32-dis.c:408:34: note: each undeclared
identifier is reported only once for each function it appears in
make[4]: *** [wasm32-dis.lo] Error 1
make[4]: *** Waiting for unfinished jobs....

which has nothing to do with my commit.


H.J.


       reply	other threads:[~2017-04-07 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1cwVGv-0000oa-E4@kwanyin.sergiodj.net>
2017-04-07 15:03 ` H.J. Lu [this message]
2017-04-07 15:32   ` Yao Qi

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='CAMe9rOoypJM6go1KhrOcdBdf7=XtZShoo3t7xKh2vT0ODTdbpg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@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