Error undefined symbol: get_vtable with FR 3.0
a.cudbardb at freeradius.org
Sat Jul 27 16:46:37 CEST 2013
On 27 Jul 2013, at 15:30, Avesh Agarwal <avesh.ncsu at gmail.com> wrote:
> On Fri, Jul 26, 2013 at 7:39 PM, Arran Cudbard-Bell <a.cudbardb at freeradius.org> wrote:
> On 27 Jul 2013, at 00:28, John Dennis <jdennis at redhat.com> wrote:
>> On 07/26/2013 06:59 PM, Avesh Agarwal wrote:
>>> While running FR3.0 and loading modules via eap_tnc, I get the following
>>> 9 [0x7f355327d840] WARN TNCS.Coordinator null - Error while initializing
>>> libtool. ???J5 : undefined symbol: get_vtable
>>> And it sometimes gives segfaults. I did not have this issue with FR2.2.0
>>> with the same set of packages. This error I am getting on both fedora 19
>>> and rhel. I am not sure what I am missing. I used the FR3.0 packages
>>> from http://koji.fedoraproject.org/koji/buildinfo?buildID=438289 .
>> Are you sure you don't have cruft lying around somewhere?
>> libtool isn't used in 3.0 and rlm_eap_tnc.so has no reference to that
> I've actually seen a similar error in rlm_unix_odbc which no longer works in 3.0 either but worked in 2.x.x. I'm not really sure what's happening.
> Does libtnc use libtool for anything?
> Not libtnc but libnaaeap use libtool.
Ok, and what's the structure of the dependencies between the libraries?
Not that i'm saying this is a solution, and I'm still not sure I understand the scoping of symbols in dynamic libraries, but have you tried calling dlopen on libtool with RTLD_GLOBAL flag? From within rlm_eap_tnc?
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
More information about the Freeradius-Users