"John Padula" <[EMAIL PROTECTED]> wrote:
> Maybe I wasn't clear, but the configure-make sequence on the new
> machine was done with a fresh 0.2 TAR file, so I tried to keep things
> consistent and only used CC throughout.
Yes, but the configure script *may& pick up gcc instead of cc.
> I exam
Alan:
Thanks for the speedy response.
> Of course, if you use 'gcc' when running 'configure',
> and 'cc' for the compile, then that would explain some
inconsistencies.
Maybe I wasn't clear, but the configure-make sequence on the new machine
was
done with a fresh 0.2 TAR file, so I tried to k
"John Padula" <[EMAIL PROTECTED]> wrote:
> I saw a posting a few weeks back about a problem with the configure
> script and $PGROOT not being properly defined.
Some of that was fixed, but not all.
> I just grabbed the latest (09/10) TAR file and configure seems to still
> be dying=20
> right a
Hello:
I saw a posting a few weeks back about a problem with the configure
script
and $PGROOT not being properly defined.
I just grabbed the latest (09/10) TAR file and configure seems to still
be dying
right around that spot (where it says "checking for PostgreSQL
includes").
Was a fix ever
