From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [obv] Fix m2-exp.y compilation error
Date: Tue, 17 Jan 2012 06:18:00 -0000 [thread overview]
Message-ID: <m38vl7cad2.fsf@redhat.com> (raw)
In-Reply-To: <20120117000845.GA26718@host2.jankratochvil.net> (Jan Kratochvil's message of "Tue, 17 Jan 2012 01:08:46 +0100")
On Monday, January 16 2012, Jan Kratochvil wrote:
> On Mon, 16 Jan 2012 22:06:46 +0100, Sergio Durigan Junior wrote:
>> --- a/gdb/m2-exp.y
>> +++ b/gdb/m2-exp.y
> [...]
>> void
>> -yyerror (msg)
>> +yyerror (char *msg)
>> char *msg;
>> {
>> if (prev_lexptr)
>
> m2-exp.y: In function ‘m2_error’:
> m2-exp.y:1069:1: error: old-style parameter declarations in prototyped function definition
>
> Recommending to always build the tree before/after a check-in.
Sorry, I had this patch lying around but should have rebuilt it anyway.
Thank you for the fix.
prev parent reply other threads:[~2012-01-17 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 22:31 [commit][obv] Remove dead code and reformat function prototype on parsers Sergio Durigan Junior
2012-01-17 1:08 ` [obv] Fix m2-exp.y compilation error Jan Kratochvil
2012-01-17 6:18 ` 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=m38vl7cad2.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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