-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exporting symbols #8
Comments
The Fedora addition looks like it is worth adding, but I would like to know what problem the openSUSE patch fixes, the base its applied to is 7 years old and I have not had a report of the code needing that from anywhere else. |
It's an old bug indeed: https://bugzilla.suse.com/show_bug.cgi?id=131175 Thought it best to be reported here anyways. |
BTW Fedora has another patch here: https://src.fedoraproject.org/rpms/unixODBC/blob/master/f/keep-typedefs.patch |
Ok, I am in agreement that leaving it here is fine, if it does come back we can deal with it then. The second Fedora patch, I am thinking to ignore. Microsoft have removed those defs from ODBC, so if the absence causes a problem building against unixODBC, the same problem will occur latter on in a Windows build. If there are still drivers out there that fail because of that, I would suggest that they add the typedefs to their own code as its their choice. |
Thanks a lot for making those symbols upstream. I guess closing this now is fine. |
I saw that both Fedora and openSUSE export some more symbols. Maybe this is something that should be upstreamed?
Fedora symbols:
https://src.fedoraproject.org/rpms/unixODBC/blob/master/f/export-symbols.patch
openSUSE exports:
https://build.opensuse.org/package/view_file/server:database/unixODBC/unixODBC-2.3.1-libodbcinst-exports.patch?expand=1
The text was updated successfully, but these errors were encountered: