No. It was a joke.
Where does this error comes from?
make[1]: Entering directory `/scratch/install/gcc-2.7.2.1/p' cc -c -DIN_GCC -DGPC -g -I. -I.. -I. -I./.. -I./../config gpc-lex.c In file included from gpc-lex.c:102: hash.h:122: `AND_' undeclared here (not in a function) hash.h:122: initializer element for `wordlist[24].token' is not constant hash.h:125: `NOT_' undeclared here (not in a function) hash.h:125: initializer element for `wordlist[27].token' is not constant hash.h:126: `NIL_' undeclared here (not in a function) hash.h:126: initializer element for `wordlist[28].token' is not constant hash.h:136: `MOD_' undeclared here (not in a function) hash.h:136: initializer element for `wordlist[38].token' is not constant hash.h:153: `DIV_' undeclared here (not in a function) hash.h:153: initializer element for `wordlist[55].token' is not constant hash.h:161: `SET_' undeclared here (not in a function) hash.h:161: initializer element for `wordlist[63].token' is not constant hash.h:176: `CONST_' undeclared here (not in a function) hash.h:176: initializer element for `wordlist[78].token' is not constant make[1]: *** [gpc-lex.o] Error 1 make[1]: Leaving directory `/scratch/install/gcc-2.7.2.1/p' make: *** [gpc1] Error 2
Cheers.
According to FPL:
No. It was a joke.
Not a good one.
Apart from my personal disappointment I get when I open this mail, I usually read and answer "it works" messages with a lower priority than cries for help. Thus the misleading subject might cause delays in the answer.
Where does this error comes from?
make[1]: Entering directory `/scratch/install/gcc-2.7.2.1/p' cc -c -DIN_GCC -DGPC -g -I. -I.. -I. -I./.. -I./../config gpc-lex.c In file included from gpc-lex.c:102: hash.h:122: `AND_' undeclared here (not in a function) hash.h:122: initializer element for `wordlist[24].token' is not constant [...]
Please make sure that your `parse.y' (or `gpc-parse.y' in old versions of GPC has the correct underscored tokens `AND_', `CONST_', etc. instead of just `AND', `CONST', etc. Then force `bison' to recompile `parse.y' by deleting (or renaming) `parse.c' before you `make' GPC.
Hope this helps,
Peter
Peter Gerwinski wrote:
According to FPL:
No. It was a joke.
Not a good one.
Apart from my personal disappointment I get when I open this mail, I usually read and answer "it works" messages with a lower priority than cries for help. Thus the misleading subject might cause delays in the answer.
I sincerly apologize if you have been hurted by what I said. When reading it again, I do understand you may have thought I complained what you do does not work. Well, What I mean is that *I* cannot make it work, what's pretty different, but once more, I do understand it is spurious.
Meanwhile, this gpc-971001.tar.gz is really painfull to install, especially this patch story, and dunno if it is an error of mine, but one installation lead the system to loose cc that was unable to run itself, and I am getting mad when I see I have installed GPC so many times but I'm just unable to do it once more, now lgcc not found, now cannot open xgpc, now I-don't-know-what... I am about downloading back the old old version I installed without any problem.
However, don't think me being such a dope I consider you are responsible for it.
Sincerly.
F.P.L
-
FPL -
Peter Gerwinski