vy wrote: > roamantic:~/continuing/_study/coreutils/lib vy$ bison -y getdate.y > getdate.y:215: unrecognized: %parse_param > getdate.y:215: Skipping to next % > getdate.y:216: unrecognized: %lex_param > getdate.y:216: Skipping to next %
This could mean the version of bison that you have installed is not sufficient. It is odd that you are running this by hand though, shouldn't this be the result of 'make' output? You should never have to invoke tools directly like that, AFAIK. > roamantic:~/continuing/_study/coreutils vy$ ./configure > --prefix=/Users/vy/local --exec-prefix=/Users/vy/local/ppc > ./configure: line 9: =======: command not found > ./configure: line 12: syntax error near unexpected token `>>' > ./configure: line 12: `>>>>>>> 1.277' This indicates that there was a conflict when you tried to update the file "configure" from cvs, and cvs indicated the conflicting hunks with those characters (which cause it to no longer be a valid shell script.) This would happen for example if you modified the file locally and then tried to patch/"cvs up" it and didn't notice the conflicts. I suggest that you start over with a fresh checkout of the source, or at the very least, do a "cvs up -C configure" (which will replace your copy of configure with the current one from the repository.) There may be other files with conflicts though. In general whenever you do a "cvs up" or apply a patch you have to look at the output of the command for files with conflicts and manually fix them by hand before they will ever build. Also it is strange that there would be conflicts on a file like configure because that is a generated file that should never be hand edited, so I don't see how you would get conflicts. Consult the CVS manual for information on conflicts, there is a whole section about this (10.3 in my copy.) You should have gotten a warning from cvs that there were conflicts (and/or seen "C" as the status character next to the filename.) Brian _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils