Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv7452

Modified Files:
	faq.sgml 
Log Message:
Add notes on dealing with bison/flex mismatch


Index: faq.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.83
retrieving revision 1.84
diff -C 2 -d -r1.83 -r1.84
*** faq.sgml	11 Jun 2009 19:03:44 -0000	1.83
--- faq.sgml	11 Feb 2010 17:51:16 -0000	1.84
***************
*** 280,283 ****
--- 280,306 ----
  
  </qandaentry>
+ 
+ <qandaentry>
+ 
+ <question> <para> I found conflicting types for <envar>yyleng</envar>
+ between <filename>parser.c</filename> and <filename>scan.c</filename>.
+ In one case, it used type <type>int</type>, conflicting with
+ <type>yy_size_t</type>.  What shall I do?</para> </question>
+ 
+ <answer><para> This has been observed on <application>MacOS</application>,
+ where <application>flex</application> (which generates
+ <filename>scan.c</filename>) and <application>bison</application>
+ (which generates <filename>parser.c</filename>) diverged in their
+ handling of this variable. </para> 
+ <itemizedlist>
+ <listitem><para> You might might <quote>hack</quote> <filename>scan.c</filename> by hand to use the matching type. </para> </listitem>
+ <listitem><para> You might select different versions of <application>bison</application> or <application>flex</application> so as to get versions whose data types match. </para> </listitem>
+ <listitem><para> Note that you may have multiple versions of <application>bison</application> or <application>flex</application> around, and might need to modify <envar>PATH</envar> in order to select the appropriate one.</para></listitem>
+ </answer>
+ 
+ 
+ 
+ </qandaentry>
+ 
  </qandadiv>