Just to be clear, it is why the ./configure script failed to produce valid results that confused me and not the exact build error. Your diagnosis corresponds with my impression, except I probably forgot to suggest deleting the config.h files ..., since I do this automatically when I run into similar odd errors. Anyway, it seems to be working for him now, so I'll let the issue rest.
Jeremy Davis [EMAIL PROTECTED] "Michael D. Pritchett" <[EMAIL PROTECTED]> wrote on 5/9/2002 2:21:55 PM: > >On Thu, 9 May 2002 [EMAIL PROTECTED] wrote: > >> .. >> >> Confused about his build problem and going to feel >> real bad when its something trivial I should have known >> about. :-) >> >> Jeremy Davis >> [EMAIL PROTECTED] >> > >Perhaps I am an idiot, but the build messages told you the specific >problem. I have no target for version.obj. This basically means it >couldn't find a version.c that was expected. version.c should be >generated through ./configure script, but configure only gets processed if >config.h is missing. > >So my guess is that in wv, config.h exists, but version.c doesn't. One >solution is to remove config.h and then reprocess. Another is to hand >modify version.c.in to a version.c and process. > >Hopefully this helps. If it was something else, drop me a note. > >Cheers! > > >Michael D. Pritchett
