On Thu, 9 May 2002 [EMAIL PROTECTED] wrote:
> > Perhaps I am mistaken, but I seem to recall him > mentioning (in private email) that he had checked out > all relevant modules and from his output below, it looks > like the build is actually entering the libiconv subdir, > that is, it appears the iconv module is being built, but > there is either an error here (that is not stopping the > build) or some other weird issue so that when wv is being > built it can't find the peer iconv headers. But hey, > if I am wrong then at least this will be an easy fix. :-) > > > 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
