Thanks for the response, Scott. Sorry you're right. I didn't phrase it well. I can see the unstatisfied symbol in xerces referencing (GLIBCXX_3.4). And i can see the symbol in libstdc++, which should satisfy that.
As it turns out your hunch was right. There are two versions of libstdc++.so.6 on my machine. Xerces built against one and xml-security built against the other. Your advice to ldd xerces illuminated the discrepancy for me. Thanks! Jake On Thu, Jul 18, 2013 at 5:38 PM, Cantor, Scott <[email protected]> wrote: > > The error I get is a bunch of undefined references like this: > > > > /opt/shibboleth-sp/lib/libxerces-c.so: undefined reference to `operator > > delete(void*)@GLIBCXX_3.4' > > > > > > This makes me think that the linker is unable to find libstdc++.so. Or, > maybe > > libxerces-c.so is built to the wrong version of libstdc++. > > The latter would be my guess. The linker doesn't have to be told to find > it, that's all automatic with g++. > > > However, I used readelf to confirm that the presence of the symbol in the > > libxerces symbol table. > > Can't be, that's not a Xerces symbol. It's an unsatisfied symbol it wants > to find at link/load time. > > > Any ideas what I might be doing wrong? > > I'd start by rebuilding xerces or at least ldd it to investigate the > binary. > > -- Scott > > >
