On 2014-05-28 19:12:44 -0400, Tom Lane wrote: > Andres Freund <and...@2ndquadrant.com> writes: > > On 2014-05-28 18:52:22 -0400, Tom Lane wrote: > >> and IMO we should also lobby the Bison people to not emit the > >> deprecation warnings yet. > > > That's a good idea. What i've been thinking about is to add > > -Wno-deprecated to the bison rule in the interim. Maybe after a > > configure test for the option. All deprecation warnings so far seem to > > be pretty unhelpful. > > Meh. If we just hide them permanently, we're likely to be blindsided > somewhere down the road when they turn a deprecation into an error.
I think some bleeding edge buildfarm animal will warn us soon enough. It's not as if we're able to do much about the deprecations as is without breaking with older releases. > What I was wondering about was if we could modify the .y files when > building with a pre-2.4 bison. It'd be easy enough to fix this with > sed, say. .oO(m4). Should be doable and might actually be interesting for a couple of other things. I think I'll just stick a BISONFLAGS=+ -Wno-deprecated in my Makefile.custom for now. I.e. I am not volunteering. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
