Bug 134839
Summary: | ODBC/mysql library symbol error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Alexandre Oliva <aoliva> |
Component: | unixODBC | Assignee: | Tom Lane <tgl> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | hhorak, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:06:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2004-10-06 17:41:46 UTC
I think this is the same issue as bug #122877. Not sure yet whether it is MyODBC or unixODBC's fault, though your idea about search path seems plausible. *** This bug has been marked as a duplicate of 122877 *** Turns out the bug is really in MyODBC. I'm not sure what those strings in libodbc are being used for, if anything at all, but the real problem was mislinkage of libmyodbc.so against its required libraries. I'm going to leave this bug classified as unixODBC anyway, because it might help lead people to the right thing if they assume it's a unixODBC problem. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |