Hallo Waldek,
Am Dienstag, 23. September 2003 um 02:23 schriebst du:
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.
It should be exactly the same output if he uses bison with the same version number... sigh.
[...]
Your error may be caused by faulty hardware -- usually I am able to
Nah, I'm the Cygwin Perl maintainer, I usually use my own compiled GCC, I can compile and use GCC with Ada, Java, ObjC, C++ and of course C, if my hardware would be a problem, I would see more difficulties than just one error when building GPC?
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.
More likely the latter. I found also that there is a file missing from the GPC source package, os-hacks.h, why isn't it included in the tarball if it is necessary to have it when compiling under Cygwin or MinGW?
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) \
I'll try that if needed, many thanks.
Gerrit