Daniel Jacobowitz sez: } On Thu, Oct 24, 2002 at 04:48:25PM -0400, Gregory Seidman wrote: } > Daniel Jacobowitz sez: } > } On Thu, Oct 24, 2002 at 04:34:07PM -0400, Gregory Seidman wrote: [...] } > } > I don't understand why my program seems to be linked to two versions of } > } > libstdc++. It looks like libstdc++.so.5 is the g++ 3.2 library, but there } > } > is also that libstdc++-libc6.2-2.so.3 which nothing seems to use. Can } > } > anyone explain this extraneous dependency? [...] } Two things to check: } } - Is it really happening? Run the application and check in } /proc/<pid>/maps for the two copies of libstdc++.
% grep libstdc /proc/19992/maps 4094a000-409d8000 r-xp 00000000 03:06 908948 /usr/lib/libstdc++.so.5.0.1 409d8000-409ef000 rw-p 0008d000 03:06 908948 /usr/lib/libstdc++.so.5.0.1 40d96000-40dcc000 r-xp 00000000 03:06 908565 /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so 40dcc000-40ddd000 rw-p 00036000 03:06 908565 /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so } - Is ldd lying? Check the libraries and app with objdump -p. Ah, yes, ldd is lying. I didn't know about objdump, but I'm glad I do now. Using objdump I find that libGLU.so.1, of xlibmesa3, is linked against that odd libstdc++. I am currently running apt-get source --compile xlibmesa3 as I type this. Thanks! } Daniel Jacobowitz --Greg
