From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-i686, revision b5a9bfbebec0a42d3c5b4fe3b7a62bd31cecc440
Date: Tue, 25 Sep 2018 13:06:00 -0000 [thread overview]
Message-ID: <87pnx1oheh.fsf@redhat.com> (raw)
In-Reply-To: <f1bea56b29c65a62495d629556ae74b4@polymtl.ca> (Simon Marchi's message of "Mon, 24 Sep 2018 12:39:35 -0400")
On Monday, September 24 2018, Simon Marchi wrote:
> On 2018-09-24 11:42, gdb-buildbot@sergiodj.net wrote:
>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../binutils-gdb/bfd
>> -DBINDIR=\"/usr/local/bin\" -DTRAD_CORE -I. -I../../binutils-gdb/bfd
>> -I../../binutils-gdb/bfd/../include -DHAVE_all_vecs -W -Wall
>> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144
>> -Werror -I../../binutils-gdb/bfd/../zlib -g -D_GLIBCXX_DEBUG-m32 -MT
>> bfdio.lo -MD -MP -MF .deps/bfdio.Tpo -c ../../binutils-gdb/bfd/bfdio.c
>> -o bfdio.o
>> <command-line>: error: ISO C99 requires whitespace after the macro
>> name [-Werror]
>> <command-line>: error: ISO C99 requires whitespace after the macro
>
> I( think we are missing a space between -D_GLIBCXX_DEBUG and -m32.
Thanks, Simon. This is fixed now.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-09-25 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 15:42 Oh dear. I regret to inform you that commit b5a9bfbebec0a42d3c5b4fe3b7a62bd31cecc440 might be unfortunate gdb-buildbot
2018-09-24 15:42 ` Breakage on builder Fedora-i686, revision b5a9bfbebec0a42d3c5b4fe3b7a62bd31cecc440 gdb-buildbot
2018-09-24 16:39 ` Simon Marchi
2018-09-25 13:06 ` Sergio Durigan Junior [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=87pnx1oheh.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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