At 04:13 PM 6/13/00 +0200, Caolan McNamara wrote:
>Is the build process not running configure in the wv directory ?
Probably not. See my message from Friday:
http://www.abisource.com/mailinglists/abiword-dev/00/June/0304.html
I strongly suggest that before adding any more ifdefs to the code, we force
configure to be rerun on that platform. (IMHO, this is actually how similar
problems got fixed for the FreeBSD and Win32 build machines.)
As mentioned, I think the long-term solution here is to make sure that this
gets taken care of for all peer libraries by triggering the appropriate
logic as part of our "make realclean" target.
However, the quick-and-easy fix is to just manually blow away *all* the
source directories on that build machine so that configure gets triggered
again.
Paul
