[EMAIL PROTECTED] wrote:
> Bruce Momjian writes:
>
> > > 1. Add options to use unixODBC in the configure.in file, the mainly consists of
>finding the root of the unixODBC install prefix, and adding
> > > -I /unixODBC/path/include and -L /unixODBC/path/lib to the driver build
>
> --with-includes,
[EMAIL PROTECTED] wrote:
> Nick Gorham writes:
>
> > Well because the driver does not know where to get the config info
> > from,
>
> Then the driver should be fixed to do that, with or without unixODBC.
Well yes, but again, using the Windows situation as a model (not that
I would normally sugge
Glad these items are being resolved. THis has sat around too long.
Please keep discussing and come up with a good patch. We will help
however we can.
> [EMAIL PROTECTED] wrote:
>
> > Nick Gorham writes:
> >
> > > Well because the driver does not know where to get the config info
> > > from,
Nick Gorham writes:
> Well because the driver does not know where to get the config info
> from,
Then the driver should be fixed to do that, with or without unixODBC.
> libodbcinst.so in unixODBC provides SQLGetPrivateProfileString,
> the location of user and system ini files are defined by thi
Bruce Momjian writes:
> > 1. Add options to use unixODBC in the configure.in file, the mainly consists of
>finding the root of the unixODBC install prefix, and adding
> > -I /unixODBC/path/include and -L /unixODBC/path/lib to the driver build
--with-includes, --with-libraries
> > 2. Change the
