Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Build regression on CentOS-5  [Re: [PATCH 3/3] add -Wold-style-definition]
Date: Wed, 10 Jul 2013 19:11:00 -0000	[thread overview]
Message-ID: <51DDB1C5.6010201@eagerm.com> (raw)
In-Reply-To: <20130710182417.GG8063@adacore.com>

On 07/10/13 11:24, Joel Brobecker wrote:
>> I'm partly of the opinion that folks with very old versions of developer
>> tools should either disable the warnings or upgrade their tools.
>> Otherwise we're letting bad versions of flex, etc, hold things back.
>
> FWIW, I agree.

Yes, me too.  Fine with me if you don't apply the patch.

I'm working on a system which has flex-2.5.4 installed, which
seems to data from 1997.  I'll build a local version.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  reply	other threads:[~2013-07-10 19:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 18:42 [PATCH 0/3] add a few new warning options Tom Tromey
2013-06-17 18:42 ` [PATCH 2/3] add -Wold-style-declaration Tom Tromey
2013-07-01 19:49   ` Tom Tromey
2013-06-17 18:42 ` [PATCH 1/3] add -Wmissing-parameter-type Tom Tromey
2013-06-17 18:59 ` [PATCH 3/3] add -Wold-style-definition Tom Tromey
2013-07-02  8:08   ` Build regression on CentOS-5 [Re: [PATCH 3/3] add -Wold-style-definition] Jan Kratochvil
2013-07-02 20:53     ` Tom Tromey
2013-07-02 20:54       ` Tom Tromey
2013-07-03  9:00         ` Jan Kratochvil
2013-07-10 16:28           ` Tom Tromey
2013-07-10 16:51         ` Michael Eager
2013-07-10 18:11           ` Tom Tromey
2013-07-10 18:24             ` Joel Brobecker
2013-07-10 19:11               ` Michael Eager [this message]
2013-06-18  5:14 ` [PATCH 0/3] add a few new warning options Joel Brobecker
2013-07-01 19:46 ` Tom Tromey

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=51DDB1C5.6010201@eagerm.com \
    --to=eager@eagerm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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