Bug 1391960

Summary:	undefined symbol: get_vtable in /usr/lib64/libtdsodbc.so.0 with freeradius-unixODBC
Product:	Red Hat Enterprise Linux 7	Reporter:	Pavel Raiskup <praiskup>
Component:	freeradius	Assignee:	Nikolai Kondrashov <nikolai.kondrashov>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Aster <jaster>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.2	CC:	databases-maint, dpal, fjayalat, gthyni, hhorak, jaster, joedward, kare.hviid, mkolaja, nikolai.kondrashov, pkis, praiskup, psklenar, qe-baseos-daemons, rupatel, trepik, vojamo
Target Milestone:	rc	Keywords:	EasyFix, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1267438
Clones:	1394787 (view as bug list)		Environment:
Last Closed:	2017-08-01 20:36:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1267438
Bug Blocks:	1289025, 1305230, 1386690, 1394787, 1399979

Description Pavel Raiskup 2016-11-04 13:47:58 UTC

There are lt_* symbols exported in FreeRADIUS binaries.  FreeRADIUS is capable
of dlopen()-ing modules which may depend on libltdl.so.* which provides the same
symbols, and this causes ugly linking issues (for more info and for reproducer
see the original bug report).

This has been fixed upstream by moving those symbols from lt_* namespace into
fr_* so they don't collide anymore.

It is worth having this backported to RHEL7:
https://github.com/FreeRADIUS/freeradius-server/issues/1277

+++ This bug was initially created as a clone of Bug #1267438 +++

Comment 6 Nikolai Kondrashov 2016-11-14 11:21:28 UTC

The patch is available upstream and linked to in #2.

Comment 11 errata-xmlrpc 2017-08-01 20:36:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1954