Red Hat Bugzilla – Bug 176950
wxGTK support for databases (wxODBC) missing
Last modified: 2009-07-02 08:58:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
The wxWidgets/GTK toolkit has a class for database abstraction via ODBC, but this class is not included in the package. It'd be nice to have it, maybe in a separate subpackage.
To compile the class --with-odbc should be added to configure.
Also it requires unixODBC (or iODBC, but iODBC is neither in Core nor in Extras).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Compile a wxGTK program that need the ODBC classes.
Actual Results: The program is compiled, but linking fails.
Other information here:
Sounds reasonable, especially since unixODBC is right there in core.
I'd like some opinions from people on whether this should be a subpackage or
integrated into the main RPM. I don't want to have a crazed profusion of
subpackages (especially when the prereqs are something that reasonably can be
expected to be on the system of someone who might want wxGTK). But does unixODBC
warrant an exception?
Matthew, is wxGTK 2.6.3 going out with or without wxODBC?
I was thinking I'd add it at that point, probably as a subpackage.
Currently with rc2, I get this build failure:
./src/common/db.cpp: In member function 'bool wxDb::Open(const wxString&, void*,
./src/common/db.cpp:848: error: ambiguous overload for 'operator=' in '((wxDb*)t
his)->wxDb::outConnectionStr = outConnectBuffer'
(Haven't investigated at all; just got that error and figured I'd mention it
here in case someone wants to jump in with a known fix.)
Hmmm, okay -- quick googling indicates that this is a problem with wxODBC and
Unicode, or at least was in 2004.
Talking to myself.... here's the upstream bug:
Building in Fedora Extras devel. Since it's currently broken and has been for so
long, I'll build for FC5 as soon as I hear positive feedback or on Monday,
whichever comes first.
Comment #8 is misplaced; sorry. Please ignore that; this is still waiting on the
I'm going to mark this deferred for now. If someone comes up with a fix, please
give me a jab and I'll revisit. Thanks!
Upstream bug not marked as fixed, but trying again with version 2.8.3 just to see.
Still broken upstream.