RE: glibc warnings

>Qt4 should still be shipped/statically linked as it's still uncommon.
>This will change when KDE 4 comes out, but for now, I think shipping
>it is the best approach.

Also, I think Qt isn't very backwards binary compatible. So if you build
with 4.2.2 and on target system user has 4.2.0 there might be problems.
That is almost anecdotal fact though, as I didn't investigate much. So
shipping them and installing private copy might be the way to go (that's
what we do).

>When I was packaging a Qt 4 app, I ended up building a custom Qt with
>apgcc. It's not that hard to do--edit the linux-g++ mkspec from the
>source tarball and change all the "g++"s to "apg++", and all the
>"gcc"s to "apgcc"s. I'm pretty sure that using an apbuild compiled
>version of Qt got rid of the errors for me.

That's what I run to build Qt with apbuild on FC6 (this is commercial
package though, so you might have to change something). I don't remember
if I had glibs warnings, but the binaries build on FC6 work fine on FC3.

#!/bin/bash
./configure -nomake examples -no-qt3support -qt-gif -no-tablet
find . -name Makefile -execdir sed -i "{s/^CC.*= gcc$/CC = apgcc/;
s/^CXX.*= g++$/CXX = apg++/; s/^LINK.*= g++$/LINK = apg++/}" '{}' ';'


---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]