Bertho Stultiens wrote:
> 
> Gerald Pfeifer wrote:
> > If wrc is built by (BSD) yacc, the build aborts with the following error:
> >
> >   ../../tools/wrc/wrc -c -s -p rsrc -s -pcomdlg32 -I. -I. -I../../include
> >   -I../../include ./rsrc.rc
> >   Error cdlg_xx.rc: 8, 1: syntax error
> >   *** Error code 1
> 
> This is a yacc issue. I am working on it (use bison for the time being).
> It has something to do with the lookahead token management, where an
> empty lookahead is "-2" for bison and "-1" for yacc. There are also a
> few other issues involved which still need to be examined more closely.
Off topic: why doesn't wrc use the "standard" gnu style for error reporting
(currently, my emacs doesn't correctly parse the error output from wrc - I
know I could fix it, but I'm too lazy). This patch would do it:

-- 
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
Index: tools/wrc/utils.c
===================================================================
RCS file: /home/cvs/cvsroot/wine/wine/tools/wrc/utils.c,v
retrieving revision 1.5
diff -u -r1.5 utils.c
--- tools/wrc/utils.c   2000/05/23 01:18:38     1.5
+++ tools/wrc/utils.c   2000/07/24 09:05:49
@@ -36,7 +36,7 @@
 
 static void generic_msg(const char *s, const char *t, const char *n, va_list ap)
 {
-       fprintf(stderr, "%s %s: %d, %d: ", t, input_name ? input_name : "stdin", 
line_number, char_number);
+       fprintf(stderr, "%s:%d:%d: %s: ", input_name ? input_name : "stdin", 
+line_number, char_number, t);
        vfprintf(stderr, s, ap);
 #ifdef WANT_NEAR_INDICATION
        {

Reply via email to