Giles Anderson wrote:
> I have upgraded Boost and find that I have to re-link my own executables.
> Should I have to? I dont really want to.
Boost API changes generally involve more than a simple relink. Their data
structures and templates frequently change, often for bugfixes. In fact,
many boo
Hi,
I'm trying to link to a library that uses different names for the static
and shared versions.
Example: libABC.so and libABCz.a
Can someone suggest a way to express this to libtool? Just passing -lABC
fails for static links; -lABCz does the wrong thing on dynamic links.
Thanks,
Daniel
_
Ralf Wildenhues wrote:
> * Daniel Herring wrote on Mon, Nov 12, 2007 at 07:46:55AM CET:
>>
>> Here's a relevant post from the GCC list; it mentions how to work around
>> some dlopen difficulties (including RTTI, exceptions, custom
>> new/delete).
>> http://gcc.gnu.org/ml/gcc-help/2007-10/msg00248.h
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Eric Gorr <[EMAIL PROTECTED]> writes:
>
>> $/Developer/usr/bin/libtool -V
>> Apple Computer, Inc. version cctools-698.1
>
> You are wrong here. What Apple calls libtool has nothing to do with GNU
libtool. You'll probably have more luck if you ask in a M
Mike wrote:
> On Tuesday 25 August 2009 12:42:19 Bob Friesenhahn wrote:
>> On Tue, 25 Aug 2009, Mike Frysinger wrote:
>> >> Relying on the OS's implicit dependency features seems to be an
>> >> approach which is fraught with peril.
>> >
>> > why ?
>>
>> When viewing the issue through Linux package-
Bob Friesenhahn wrote:
> While it has not been proven yet, I am suspecting that the failing C++
> exceptions have something to do with the way that libtool links these
> modules.
>
> Does anyone have ideas about this?
Do all exceptions fail, or just some exceptions?
For example, does something li
