I am having all sorts of problems with shared libraries and C++ with the multi-lang. branch. PROBLEM 1 1) On many platforms libtool can create shared libraries for C but not for C++ 2) On many of the platforms which libtool does know how to create C++ shared libraries libstdc++ is not compiled as a shared library, nor is it compiled with PIC support. This means that linking the shared library fails miserably because it will try to link the non PIC code into the shared library. So my question is 1) Is there a way to force libtool NOT to link it as a C++ library if it can't do it as a shared library. IE don't fall back to only making a static library. 2) Is there a way to force libtool NOT to link in libstdc++ but STILL link it using c++? In either case I would like the C++ libraries to be specified in the .la files so that they will get statically linked in by libtool when a C program uses my libraries. PROBLEM 2 Is they a way to do the ldpreloding stuff that is 100% transparent to programs linking with my libraries using libtool? I want the end user to have to doing noting but "libtool --mode=link ... -l<My library>" and have libtool automatically preload the necessary modules and set up the data structure automatically so that the end user does NOT have to call LTDL_SET_PRELOADED_SYMBOLS(). Thanks in advance. Any advice you can give me would really help me out with my Pspell (http://pspell.sourceforge.net) project. --- Kevin Atkinson [EMAIL PROTECTED] http://metalab.unc.edu/kevina/
