Linking with -lgcc solved my problem (my symbol was __builtin_vec_new).
Strange enough, my version of libsablot.so doesn't require _any_ rtti
symbol.
Pavel Hlavnicka wrote:
> It doesn't look good. I've just tried it on our test freeBSD account
> with similar results (with another unresolved function). It is strange,
> because as far as I remember it worked, but then something happened :(
>
> Problem is with linking of C++ library (Sablotron) to C (Perl
> extension). While linker links Sablotron, is supposes, that linker of
> final executable takes care for special C++ symbols.
>
> On my platform (RH 6.2 gcc 2.91.66) are problematic symbols resolved
> inside the library. On FreeBSD not (I've tested FreeBSD 3.4 with gcc of
> 2.7.2.3).
>
> Solution? I dunno... Try to find out, if problematic symbol is defined
> in some system libaray and add it to library list in Makefile.PL. If
> this function is not defined in any library and is implemented as
> compiler 'magic', the problem is serious.
>
--
Pavel Hlavnicka
Ginger Alliance Ltd.
Prague; Czech Republic
