Re: glibc warnings

2007/11/28, Justin Karneges <[email protected]>:
> Hi,
>
> I'm trying to build all of our deps with apbuild (openssl, zlib, Qt4), and
> I've mostly succeeded.  I can makepackage a test application using QtCore and
> it succeeds without warnings.  However, when I use QtGui, then I'm given
> this:

Do you really need to ship Qt? I think it is better to link
dynamically to QT and use whatever version the user already has on his
system. That way this problem will go away.
zlib is also a system library that all users already have (gzip
depends on it, and so does a lot of other base tools). No need to
build and ship it - just link dynamically.

OpenSSL is bad to ship because it is a security library and if you
ship it, the user won't benefit from the system upgrades.

> "WARNING: Symbols from glibc 2.3 (or newer) were found. Consider using apbuild
> to allow users of older distros to run this binary.  If you are statically
> linking any libraries, make sure they are compiled with apbuild too."

As you mentioned, its probably the X11 libs. I'm not sure you want to
go through an X11 recompile though :-)

You might be able to force QT to dynamically link to X, by setting
APBUILD_NO_STATIC_X to 1. See http://autopackage.org/apbuild-apgcc.php

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