Re: Library names on Unix

> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)net]
> Sent: 04 January 2006 00:27
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Library names on Unix
>
> Am Dienstag, 3. Januar 2006 09:41 schrieb Dave Page:
> > BTW, if you're hacking the build system, would you mind adding a
> > --with-pgsql= option to configure? The current code you
> wrote relies on
> > pg_config being in the path which it certainly isn't on many of my
> > systems.
>
> The magic spell is configure PG_CONFIG=/path/pg_config. This
> is the same
> mechanism by which you can override the path name of any
> other program in any
> configure script.

Thanks, but './configure --help' won't tell users that, nor is it
particularly consistent with other configure scripts which typically
offer options to specify the location of other code/libraries in
addition to having the undocumented ability to take things from the
environment. For example, we wouldn't expect users to configure the
location of SSL via an envvar when building the server.

Regards, Dave