Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 122877 (IT#36528)

Summary:	/usr/lib64/libmyodbc.so: undefined symbol: _dig_vec
Product:	Red Hat Enterprise Linux 3	Reporter:	Ben Levenson <benl>
Component:	MyODBC	Assignee:	Tom Lane <tgl>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	aoliva, hhorak, tao
Target Milestone:	---
Target Release:	---
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-05-19 23:37:02 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 Ben Levenson 2004-05-09 22:08:41 UTC

Description of problem:
I noticed this problem while testing unixODBC on s390x and x86_64:
# /usr/bin/dltest /usr/lib64/libmyodbc.so
[dltest] ERROR: /usr/lib64/libmyodbc.so: undefined symbol: _dig_vec

Version-Release number of selected component (if applicable):
2.50.39-12
platforms: s390x and x86_64

works as expected on x86, ia64, ppc

Comment 1 Alexandre Oliva 2004-10-06 22:00:29 UTC

*** Bug 134839 has been marked as a duplicate of this bug. ***

Comment 3 Tom Lane 2004-11-11 20:45:24 UTC

Turns out that libmyodbc.so was being built without any dependency on
libraries in /usr/lib64, due to using an obsolete version of libtool.

Fixed in MyODBC-2.50.39-12.1.

Comment 6 Tim Powers 2005-05-19 23:37:02 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-441.html