>Can you check that you don't have another bison in your path?
>
>Make sure that you don't use text mounts.
>
>Sorry, I cannot reproduce. It builds here in the same configuration.
>
> Volker
Volker, thanks for kindly reply.
I have used the right bison, and the cygdrive is binmode
The bison report is:
$ bison -v parser.y
parser.y: conflicts: 5 shift/reducev
State 0 conflicts: 1 shift/reduce
State 6 conflicts: 1 shift/reduce
State 161 conflicts: 1 shift/reduce
State 221 conflicts: 1 shift/reduce
State 284 conflicts: 1 shift/reduce
I have tried several version of bison and 2 version of parser.y
and get all the same conflicts.
see the following table.
parser.y:
OOo_1.1.4 OOo_2.0beta
bison:
1.875(2003-1-1) 1 shift/reduce 5 shift/reduce
1.875b 1 shift/reduce 5 shift/reduce
1.875e 1 shift/reduce 5 shift/reduce
2.1 1 shift/reduce 5 shift/reduce
I now do the bisoning manually (ignore the conflicts),
and then comment the YACCTARGET lines in makefile,
and then go on dmaking.
I am not sure whether it is safe or not. It runs on my machine.
The same problem occured on handling module RSC and CONNECTIVITY.
rsc/source/parser/rscyacc.y
connectivity/source/parse/sqlbison.y
And the same solution to them.
It took me so long a time to get it running.
