This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Undefined symbol confusion
- From: Burlen Loring <burlen dot loring at kitware dot com>
- To: binutils at sourceware dot org
- Date: Fri, 17 Oct 2008 08:58:06 -0400
- Subject: Undefined symbol confusion
Hi all,
I have ran into another strange (at least to me) undefined symbol
situation. What I don't understand is why these symbols are undefined,
because when the library was linked there was a "-l" that pointed to the
library containing these symbols. Here is what I am talking about:
tycho:~/ext/kitware_cvs/PV3-VTK$nm -C bin/libvtkCommonPythonD.so | grep
'vtkDirectory::FileIsDirectory'
U vtkDirectory::FileIsDirectory(char const*)
tycho:~/ext/kitware_cvs/PV3-VTK$ldd bin/libvtkCommonPythonD.so
...
libvtkCommon.so.5.3 =>
/home/burlen/ext/kitware_cvs/PV3-VTK/bin/libvtkCommon.so.5.3 (0xb7981000)
...
tycho:~/ext/kitware_cvs/PV3-VTK$nm -C bin/libvtkCommon.so.5.3 | grep
'vtkDirectory::FileIsDirectory'
0016a5ee T vtkDirectory::FileIsDirectory(char const*)
How can this symbol be undefined in libvtkCommonPythonD.so, when the
library it is defined in is linked in?
By the way, I have no problem using dlopen in a stand alone app to load
the library without any extra "-l" so I wonder if this symbol is really
undefined? or if it's just a descrepency in nm?
Burlen