Bug 1391960 - undefined symbol: get_vtable in /usr/lib64/libtdsodbc.so.0 with freeradius-unixODBC
Summary: undefined symbol: get_vtable in /usr/lib64/libtdsodbc.so.0 with freeradius-un...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: freeradius
Version: 7.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Nikolai Kondrashov
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On: 1267438
Blocks: 1289025 1305230 1386690 1394787 1399979
TreeView+ depends on / blocked
 
Reported: 2016-11-04 13:47 UTC by Pavel Raiskup
Modified: 2020-03-11 15:20 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1267438
: 1394787 (view as bug list)
Environment:
Last Closed: 2017-08-01 20:36:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1954 0 normal SHIPPED_LIVE freeradius bug fix and enhancement update 2017-08-01 18:29:54 UTC

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
Note You need to log in before you can comment on or make changes to this bug.