*.gperf files in gcc directories?

Iain Woolf iainw@nortelnetworks.com
Wed Aug 25 19:30:00 GMT 2004


Hi all,

  I see a number of gperf files in the gcc source directory:

./gcc/ch/gperf
./gcc/cp/gxx.gperf
./gcc/c-gperf.h
./gcc/c-parse.gperf
./gcc/java/keyword.gperf
./gcc/objc/objc.gperf

And I notice that some header files have been produced by calling gperf 
on these files with various options.

However, the gperf step isn't part of the build, so my question is when 
should one "re-gperf" the above files, if at all?

I'm running into the following error when building a gcc cross compiler 
on linux:

gcc -c -DCROSS_COMPILE -DIN_GCC -DHAIFA    -DCPU=PPC860  -DHAVE_CONFIG_H 
    -I. -I../../gcc -I../../gcc/config -I../../gcc/../include 
../../gcc/c-lex.c
In file included from ../../gcc/c-lex.c:170:
c-parse.gperf:89: `VEC_STEP' undeclared here (not in a function)
c-parse.gperf:89: initializer element is not constant
c-parse.gperf:89: (near initialization for `wordlist[132].token')
make[1]: *** [c-lex.o] Error 1
make[1]: Leaving directory 
`/localdisk/data/tornado2.2-cp1-20040816/host/src/gnu.ppc/linux-build/gcc'
make: *** [all-gcc] Error 2


At line 170, c-lex.c includes c-gperf.h which was produced by gperf 
processing the file c-parse.gperf.


Any ideas?

  Iain



More information about the Gcc-help mailing list