In general this can be solved by doing a
make distclean
which should be included in the makefile, which is supposed to kill all
of the config.cache and generated targets created in the configure step.
Sorry if this is already answered, just joined.
-bill
On Wed, 10 May 2000, Travis Bauer wrote:
> Thanks for all the advice. The following was _exactly_ the problem. I
> had tried to compile this source code in a recent version of solaris. It
> compiled flawlessly, but postmaster wouldn't start up. So I just did a
> secure shell to a linux machine, ran "make clean" from the same directory,
> and ran configure. I thought make clean would erase all except the
> distribution files. It compiled, installed, and I used psql
> to get into the database. I haven't tested the ODBC or the JDBC
> interfaces yet (I'm using both in my projects), but all seems to be
> working.
>
> Thanks,
>
> ----------------------------------------------------------------
> Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer
> ----------------------------------------------------------------
>
> On Wed, 10 May 2000, Culberson, Philip wrote:
>
> >
> > I found that once configure has found an item it is looking for, it caches
> > it in config.cache. From then on, even if you do a "make clean", configure
> > still uses things from config.cache.
> >
>
>
