Subject | [Fwd: Re: [firebird-python] kinterbasdb 3.2.1] |
---|---|
Author | Pavel Cisar |
Post date | 2008-08-05T09:43:06Z |
Answer from Alex sent off the list...
On Friday 11 July 2008 14:07, you wrote:
> Alex Peshkov napsal(a):
> > In 2.1 there are no changes in firebird build environment, but there are
> > minor changes in fbclient build process. This library is statically
> > linked with libstdc++ now - this makes it much better usable with other
> > libraries, using another versions of libstdc++. Linker used is gcc, not
> > g++ - in order to avoid automatically added dynamic libstdc++, at the
> > same time having the rest of functions linked dynamically.
>
> Obviously, it's the reason why KI import fails, as _Unwind_GetIP comes
> from this statically linked library. But I don't understand why it's ok
> on 64bit version of SuperServer but has issues with 32bit. Is Firebird
> client linked dynamically on 64bit or what's going on here? I'm
> attaching build logs from KInterbasDB on 64bit and 32bit platforms.
>
> > I'll be away for 2 or 3 weeks since Monday, afterwards I can take a
> > closer look at a problem - provided you prepare me full test case (I'm
> > not python programmer).
>
> Test case is simple. To build KInterbasDB, just download the source
> package, unpack it and execute as root: python setup.py build
> to install it, run python setup.py install
> (it would also build it if it isn't)
> You would also need Python (2.5 or 2.4) and Firebird installed :-)
>
> Then start the python interpreter and issue:
> >> import kinterbasdb
I've reproduced a problem with Fedora6 linux. The reason why behaviour
can differ is that sometimes python interpreter itself contains
reference to libgcc_s.so (where _Unwind_GetIP is defined), but sometimes
- not.
Obviously we must add such a reference to our client library. Will do it
soon. As a fast help LD_PRELOAD can be used.
A.