Re: glibc warnings
Justin Karneges <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday 28 November 2007 2:07 am, Isak Savo wrote: > 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. As another wrote, not all systems have Qt 4. I also specifically need Qt 4.2 (interface version). Of course it is better to use the system Qt if available. Ideally my application would link dynamically to Qt, and then the autopackage would determine if Qt 4.2+ is already present. If it isn't, then there'd be some internal qt.package file that gets installed. However, I haven't figured out how to do that yet so I thought the easiest approach would be to do a static build. > 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. And the same for OpenSSL. Ideally dynamic, with a dynamic lib installed by autopackage as necessary. Until I figure this out, static seems like a simple route. > > "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 :-) I don't? This seems to contradict the autopackage documentation, which talks about how apbuild is used to statically link X11 libs. > 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 It already links dynamically by default. I forced static linkage with APBUILD_STATIC. Either way, I get glibc warnings. -Justin --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]