From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Library names on Unix |
Date: | 2006-01-03 15:20:43 |
Message-ID: | 15770.1136301643@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> 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. I don't object to that being the default behaviour, but it
> would be handy to override it when necessary.
Agree about the usefulness, but --with-pgsql seems a too generic name in
this context (it could equally well refer to the location of a PG source
tree, say). How about something like
--with-pg-config=/opt/pgsql/bin/pg_config
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Biser | 2006-01-03 19:40:45 | Parameters.Refresh error. |
Previous Message | noreply | 2006-01-03 12:43:18 | [ psqlodbc-Bugs-1000510 ] Access the rdoResultsets column is NULL in the second access |