Re: libtool problem with Solaris C++ templates

[Ossama Othman <othman@cs.wustl.edu>]

Hi,

You might want to move your discussion to the libtool mailing list
since this is a libtool issue.

On 19 May, Ron O'Hara wrote:
 > I've just come across a nasty problem.
 > 
 > The Solaris WorkShop Pro C++ compiler is very picky about the names of
 > object files.
 > 
 > The project I'm working on, uses C++ templates extensively (from
 > RogueWave). We have been having difficulty making the linker instansiate
 > the methods on objects in shared libraries created by libtool. It turns
 > out that the linker DOES instantiate them if the input files end in .o but
 > does NOT instatiate them if they have been moved to a .lo suffix (by
 > libtool).

Aha!  You've confirmed my findings!  Libtool's C++ support still needs
alot of work.  Some of us have been working on contributions for
improving libtool's C++ support.  Unfortunately, I haven't had much
time to work on it lately, despite the fact that I need the C++ support
desperately. The libtool maintainers are also overworked so we can't
ask too much them (can we? :).

Any contributions are very welcome.  Look for "C++ support" in the
libtool mailing list archive for more information about where C++
support stands.

-Ossama
-- 
Ossama Othman <othman@cs.wustl.edu>
Center for Distributed Object Computing, Washington University, St. Louis
58 60 1A E8 7A 66 F4 44  74 9F 3C D4 EF BF 35 88  1024/8A04D15D 1998/08/26