Error undefined symbol: get_vtable with FR 3.0
Hello, While running FR3.0 and loading modules via eap_tnc, I get the following errors: 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 . Thanks Avesh
On 07/26/2013 06:59 PM, Avesh Agarwal wrote:
Hello,
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
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 symbol. -- John
On 27 Jul 2013, at 00:28, John Dennis <jdennis@redhat.com> wrote:
On 07/26/2013 06:59 PM, Avesh Agarwal wrote:
Hello,
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
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 symbol.
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? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
On Fri, Jul 26, 2013 at 7:39 PM, Arran Cudbard-Bell < a.cudbardb@freeradius.org> wrote:
On 27 Jul 2013, at 00:28, John Dennis <jdennis@redhat.com> wrote:
On 07/26/2013 06:59 PM, Avesh Agarwal wrote:
Hello,
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
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 symbol.
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.
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 27 Jul 2013, at 15:30, Avesh Agarwal <avesh.ncsu@gmail.com> wrote:
On Fri, Jul 26, 2013 at 7:39 PM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 27 Jul 2013, at 00:28, John Dennis <jdennis@redhat.com> wrote:
On 07/26/2013 06:59 PM, Avesh Agarwal wrote:
Hello,
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
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 symbol.
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@freeradius.org> FreeRADIUS Development Team
Avesh Agarwal wrote:
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
9 [0x7f355327d840] WARN TNCS.Coordinator null - Error while initializing libtool. ???J5: undefined symbol: get_vtable
You're using tncs, which isn't a supported module. You're also using libtool. The server does not use libtool any more. You need to fix your build system so that it doesn't use libtool to build the rlm_eap_tnc module. Alan DeKok.
On 27 Jul 2013, at 16:08, Alan DeKok <aland@deployingradius.com> wrote:
Avesh Agarwal wrote:
While running FR3.0 and loading modules via eap_tnc, I get the following errors:
9 [0x7f355327d840] WARN TNCS.Coordinator null - Error while initializing libtool. ???J5: undefined symbol: get_vtable
You're using tncs, which isn't a supported module. You're also using libtool. The server does not use libtool any more.
You need to fix your build system so that it doesn't use libtool to build the rlm_eap_tnc module.
Does libtool add a load of magic shit to the shared libraries that gets run when they're loaded? Or when you call a function in them? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
Arran Cudbard-Bell wrote:
Does libtool add a load of magic shit to the shared libraries that gets run when they're loaded? Or when you call a function in them?
No one knows. And I don't care to look. Maybe he's also using a C++ library. Which doesn't really interact well with a C executable. Alan DeKok.
On 27 Jul 2013, at 16:29, Alan DeKok <aland@deployingradius.com> wrote:
Arran Cudbard-Bell wrote:
Does libtool add a load of magic shit to the shared libraries that gets run when they're loaded? Or when you call a function in them?
No one knows. And I don't care to look.
Maybe he's also using a C++ library. Which doesn't really interact well with a C executable.
He is. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
Arran Cudbard-Bell wrote:
Maybe he's also using a C++ library. Which doesn't really interact well with a C executable.
He is.
Ah. Then the answer is largely "tough". C++ executables can link to C libraries. C executables can't link to C++ libraries. He'll need to build FreeRADIUS with a C++ compiler, which makes it a C++ executable. Good luck with that. Alan DeKok.
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Avesh Agarwal -
John Dennis