portability fix for bison-1.75

Mark Linimon linimon at lonesome.com
Sun Jan 22 23:09:25 PST 2006


On Sun, Jan 22, 2006 at 10:19:34PM -0800, Paul Eggert wrote:
> Yes, in both cases.  I'll follow up separately for each one.
> Briefly, Pike is doing a "#define short int", which violates
> section 7.1.3 of the C Standard, and bro is doing a
> "#define YYLLOC_DEFAULT(Current, Rhs, N) Current = Rhs[N];",
> which doesn't properly parenthesize the right-hand side of the macro.
> 
> I'll check whether the bugs are still in the latest versions of these
> programs, and if so I'll send a bug report to the upstream developers.
> 
> However....
> 
> As far as I can tell, neither Pike 7.0 nor bro 0.8 is currently being
> maintained by the upstream developer, so what procedure would you
> prefer here, to make Bison 2.1 acceptable to you?  Should I send you a
> patch for these programs personally?

Just send-pr and we'll try to catch them as they come in.

mcl


More information about the freebsd-ports mailing list