Re: glibc warnings
Justin Karneges <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thursday 29 November 2007 2:50 am, Gabriele Greco wrote: > > Everything is built using apbuild, so I don't know why I get this > > warning. Is > > there a way to investigate this further? Maybe I can find out if > > libQtGui.so > > is the culprit, and see what about my compilation of that lib went > > wrong. My > > guess is that maybe the X libs are making these references. I didn't > > build > > the X libs myself, I'm just using the static versions on my distro (using > > APBUILD_STATIC). > > I solved similar problems with: > > APBUILD_NO_STATIC_X=1 Yes, now it works for me. I totally misunderstood what was going on here. I thought X wasn't being linked statically, because I'd see SM, ICE, X11, etc as dynamically linked. As it turns out, there are some X libraries that autopackage does indeed link statically. By enabling APBUILD_NO_STATIC_X=1, I can see now many more libraries being linked dynamically, and this solves the glibc warnings. I still get a warning about how I should statically link to Xrender. Isak wonders if maybe this is a useless warning now. APBUILD_STATIC=Xrender gets rid of the warning, but I've decided to ship with the dynamic Xrender until I'm told otherwise, since all other X libs are dynamic. -Justin --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]