Gerrit P. Haase wrote:
What is very new in this case or better , which is the correct versin? I have `bison (GNU Bison) 1.875b'.
With this it fails:
<snip> I get the same errors (in fact most of the messages are warnings). If I apply the patch below to 'parse.y' the build goes OK for me. Frank have bison with the same version number but which makes slightly different output.
I have succesfully compiled cross-compiler from linux to Cygwin and then cross-compiled Cygwin gpc on Linux box. I had errors in the build process since I first incorrectly installed Cygwin header files, also I have not checked if the binaries produced by the compiler work. In fact some problems are expected as with gcc-3.3.x gpc have no preprocessor predefines (as Maurice Lombardi noticed) and Cygwin uses some predefines.
Your error may be caused by faulty hardware -- usually I am able to reproduce errors using cross-compiler. It may also be another memory management problem. I will try if I can build gpc on Cygwin, but I have limited access to Windows machines so it will take some time.
diff -ru gpc-20030830.orig/p/parse.y gpc-20030830/p/parse.y --- gpc-20030830.orig/p/parse.y Sun Sep 14 02:15:08 2003 +++ gpc-20030830/p/parse.y Tue Sep 23 01:14:19 2003 @@ -65,7 +65,7 @@
%{ #include "gpc.h" - +#undef abort /* A few keywords of some dialects can be parsed as regular identifiers and checked from the parser actions => fewer special tokens. */ #define ASSERT_ID(id, location, pseudo_keyword) \