Re: compiler warnings in ODBC

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: compiler warnings in ODBC
Date: 2001-11-05 20:00:39
Message-ID: 3BE6EFE7.22DD2C2B@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
>
> Hannu Krosing writes:
>
> > > Btw., to get the iODBC driver, you need both options --with-iodbc and
> > > --enable-odbc. If you only use the former, you get nothing at all.
> > > Again, this could conceivably be done differently.
> >
> > --enable-odbc=standalone
> > --enable-odbc=iODBC
> > --enable-odbc=unixODBC
> >
> > could be the logical way to do it ?
>
> Logical maybe, but not consistent with typical configure options. If you
> want to build your package while using some other package for it, then the
> option is --with-package. I could imagine making --enable-odbc optional
> in that case, though.
>

My understanding was that different ODBC variants were mutually
exclusive
while other packages are not. Thus a separate option. it could be also

--with-odbc=xxxODBC or --enable-odbc=xxxODBC

------------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-11-05 20:04:46 Re: Licensing issues including another projects source
Previous Message Dave Cramer 2001-11-05 19:59:43 Re: Licensing issues including another projects source code into the jdbc driver