Qt-interest Archive, July 2007
libqui and libstdc++.so.6 (and 5)
Message 1 in thread
hello everyone,
if i am not mistaken libqui for qt-3.3.4 and 3.3.6 is compiled based on
libstdc++.so.5 . correct?
so if i compile my application with libstdc++.so.6 ... the probably will be
some problem right?
thing is i have this application that i started development on last year.
since it is running on an embedded arm processor, the normal step for me is
to compile the arm executable through scratchbox. so far no problem had
shown up.
however, i recently had to re-install scratchbox from scratch and the
toolchain contains libstdc++.so.6 instead of 5.. obviously if i had the old
toolchain i would have used that instead that had the v5 instead of the v6,
but i dont.
so i recompiled as always the application and it did so smoothly. only a
warning message came up saying:
then i went on to run the app. it required v6 of the lib to be run so i
provided that too.. it did run smoothly for the first few hours... but some
time overnight it 'froze' for the 1st time...
so im thinking that its possible there is problem with the different
versions, and that i should try to have the 'same' of these. and i have
tried ALOT to find the old toolchain with no luck... i also tried compiling
the QTlib from scratch inside scratchbox and it fails to compile in so many
ways...
so i will ask.. is there a version of qt-3.3.4 or 3.3.6 that was compiled
with libqui based on libstdc++.so.6 ?
thank you for your help
nass
Message 2 in thread
)\(@sS wrote:
> hello everyone,
> if i am not mistaken libqui for qt-3.3.4 and 3.3.6 is compiled based on
> libstdc++.so.5 . correct?
This depends on the platform, version, and toolchain. It'll be built
with whatever's appropriate for the target host.
> so if i compile my application with libstdc++.so.6 ... the probably will be
> some problem right?
Well, you can expect problems if you use C++ APIs to communicate between
a library built & linked against libstdc++ 5 and an app built and linked
against libstdc++ 6, yes.
> since it is running on an embedded arm processor
Aah, you're doing embedded development work.
> so im thinking that its possible there is problem with the different
> versions,
That's highly likely.
> and that i should try to have the 'same' of these. and i have
> tried ALOT to find the old toolchain with no luck... i also tried compiling
> the QTlib from scratch inside scratchbox and it fails to compile in so many
> ways...
Some more details would be good here. In the end, I suspect you'll want
to know how to compile Qt for your target platform anyway (since you'll
want to make a cut-down version with only the parts you actually use) so
it might be a good time to learn how to build it.
By the way, your mail client is sending a totally bogus realname in your
From: address. Might want to fix that.
--
[ signature omitted ]
