Adriaan van Os wrote:
find . -name "config-lang.in" in the gcc source directory did not show anything for gcc/p. the p directory had to be copied to gcc.
Can anybody add a note to compilation instructions (http://www.gnu-pascal.de/gpc/Compiling-GPC.html)? the note should say any think like: find . -name "config-lang.in" | xargs grep language= should return a line with pascal: ./gcc/p/config-lang.in:language="pascal" (this would save me fair amount of time of searching around all different manuals)
The documentation mentions moving the directory:
: @samp{cd} to the GPC directory and move the contents (a subdirectory : @file{p}) to the subdirectory @file{gcc} of the GCC directory: : : @smallexample : % mv /home/fred/gpc-20030209/p /home/fred/gcc-2.95.3/gcc/ : @end smallexample : : Instead of moving the directory, it is now also possible to make a : symbolic link (if the OS supports symlinks). This is useful if you : want to build GPC with several different GCC versions: : : @smallexample : % ln -s /home/fred/gpc-20030209/p /home/fred/gcc-2.95.3/gcc/p : @end smallexample
http://www.microbizz.nl/gpc332d1.src.tar.bz2 includes detailed building instructions.
Now the GPC configures and starts to compile. Next obstacle is bison error in parse.c (USE_ASSERT_RATHER_THAN_ABORT).
You need a special version of bison. Frank Heckenbach can tell you which one.
Lets see the bison package will be updated. (bison-2.0 was released on 04-Jan-2005)
Yes, fortunately we now have a stable bison version that we can use. I've checked that GPC works properly with it. So hopefully we're at least done with that ugly alpha/beta dependency.
So I recommend getting bison-2.0 (ftp://ftp.gnu.org/gnu/bison/bison-2.0.tar.gz) and using it for all GPC compilations.
Frank