Kjell-Olav,
On Thu, Oct 31, 2002 at 12:50:55PM -0500, Jason Tishler wrote:
> On Thu, Oct 31, 2002 at 06:10:12PM +0100, kob@norkart.no wrote:
> > Thanks for helping:
>
> No problem -- actually, you are helping me.
Would you be willing to try another workaround?
> > gcc -v -o conftest conftest.c -lcygipc output:
> >
> > Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
> > [snip]
> > /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/ld: cannot find -lcygipc
> > collect2: ld returned 1 exit status
>
> The above implies that Cygwin gcc 3.x is not automatically searching
> for libraries in /usr/local/lib. BTW, I just tried under Linux gcc
> 3.x and it does not search /usr/local/lib either.
>
> You can try the following workaround:
>
> $ ln -s /usr/local/lib/libcygipc.a /usr/lib
If so then, then delete the above symlink and then configure as follows:
$ LDFLAGS=-L/usr/local/lib configure --enable-multibyte ...
^^^^^^^^^^^^^^^^^^^^^^^^
By reading configure, it seems that defining LDFLAGS as above should
enable PostgreSQL 7.2.3 to configure successfully under gcc 3.x. Does
it?
> while I try to figure out the best long-term solution.
Actually, I checked PostgreSQL CVS and I think that PostgreSQL 7.3 and
later will no longer have this problem.
Thanks,
Jason