From: | <noreply(at)pgfoundry(dot)org> |
---|---|
To: | noreply(at)pgfoundry(dot)org |
Subject: | [ psqlodbc-Bugs-1010833 ] '--without-iodbc' enables iodbc support |
Date: | 2010-09-25 13:29:33 |
Message-ID: | 20100925132933.9D87610715CF@pgfoundry.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Bugs item #1010833, was opened at 2010-06-01 03:17
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010833&group_id=1000125
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Aaron Swenson (titanofold)
Assigned to: Nobody (None)
Summary: '--without-iodbc' enables iodbc support
Initial Comment:
Adding --without-iodbc to configure options causes same behavior as --with-iodbc.
----------------------------------------------------------------------
>Comment By: Aaron Swenson (titanofold)
Date: 2010-09-25 13:29
Message:
Sorry, I should have given a bit more detail.
This is regarding a Gentoo ebuild:
https://bugs.gentoo.org/show_bug.cgi?id=50368
There's a function, $(use_with useflag), that returns
--with-useflag or --without-useflag depending on the status
of useflag.
Rather than using that single line function, I have to write
a conditional block and add a variable in order to store
either --with-iodbc or --with-unixODBC
----------------------------------------------------------------------
Comment By: Hiroshi Inoue (hinoue)
Date: 2010-06-03 03:40
Message:
Hmm may be a buf of the configure script.
I would check it.
However iodbc and unixODBC can't coexist and
--with-unixODBC implies --without-iodbc.
What do you intend by --without-iodbc option?
----------------------------------------------------------------------
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010833&group_id=1000125
From | Date | Subject | |
---|---|---|---|
Next Message | Marco Aurelio Zoqui | 2010-09-25 19:41:07 | How to use by-passing the installation |
Previous Message | noreply | 2010-09-24 03:59:45 | [ psqlodbc-Bugs-1010837 ] 2000 is returned instead of actual info for char column octet length and column size |