From: mental@... Date: 2006-01-05T02:36:59+09:00 Subject: Re: building parse.o Quoting Lou Vanek : > why are you running gperf? lex.c should have come with the rest > of the code already pre-assembled (it did for me). Blame HP-UX's make. > The entire file, lex.c, is pretty much generic C code. There > shouldn't be any need to re-generate the file unless you are > adding new keywords into the Ruby language. It turns out I've got two problems: 1. HP-UX's make considers a file out-of-date if it is the same age as its dependencies -- since lex.c is unpacked with the same timestamp as keywords, /usr/bin/make decides that it needs to be regenerated. 2. The build of gperf on this box is badly broken Workaround: touch lex.c before building. Lesson: Always use gmake. -mental