From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [Patch] Fix binutils-gdb build with GCC 4.9 (was: Build problems with GIT version: ../bfd/bfd.h:304:75: error: right-hand operand of comma expression has no effect)
Date: Wed, 29 Jan 2014 14:34:00 -0000 [thread overview]
Message-ID: <20140129143448.GA29560@physik.fu-berlin.de> (raw)
In-Reply-To: <20140129125618.GA28587@physik.fu-berlin.de>
Dear gdb-patches readers,
please ignore my patch. It has been fixed differently by
Nick (thanks!):
https://sourceware.org/ml/binutils/2014-01/msg00334.html
[Already committed and, unsurprisingly, it works like a charm.]
(I thought I mention it here as his email only went to
binutils.)
On Wed, Jan 29, 2014 at 01:56:19PM +0100, Tobias Burnus wrote:
> GCC 4.9 (current GIT version) seems to warn now about
> bfd_set_section_userdata (stdoutput, seg, seginfo);
> where the macro expands to "..., TRUE" (-Wunused-value)
Tobias
next prev parent reply other threads:[~2014-01-29 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140128082513.GA25073@physik.fu-berlin.de>
2014-01-29 12:56 ` Tobias Burnus
2014-01-29 14:34 ` Tobias Burnus [this message]
2014-01-30 4:17 ` Joel Brobecker
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=20140129143448.GA29560@physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.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