forgotten C/OBJ parser update breaks cc1obj

[Kaveh R. Ghazi]

 > From: "David S. Miller" <davem@redhat.com>
 > 
 > The following change:
 > 
 > 1999-12-17 13:21 -0800  Zack Weinberg  <zack@rabi.columbia.edu>
 > 
 >  ...
 > 
 > 	* c-parse.in (string action): Do not warn about ANSI string
 > 	concatenation in system headers.  Affects C parser only.
 > 	* c-parse.y, c-parse.c, c-parse.h: Rebuild.
 > 
 > Indicates that only the C parser should be rebuilt, this is completely
 > wrong because objc is now expecting different identifier codes than
 > what the rest of the C front-end it shares does.  For example:
 > 
 > ? egrep PLUSPLUS c-parse.c objc/objc-parse.c | grep define
 > c-parse.c:#define	PLUSPLUS	299
 > objc/objc-parse.c:#define	PLUSPLUS	300
 > ?
 > 
 > Please fix this and in the future rebuild all files dependant upon
 > c-parse.y when you change it.  Thanks.


Looks like Zack used bison-1.28 to build c-parse.c whereas
objc-parse.c was previously built with 1.25.

Does it matter which particular version of bison we use, or are we
okay as long as we are consistent across both C & Objc?

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions