On Thu, Mar 23, 2006 at 04:33:22PM +0100, Laszlo Boszormenyi wrote: > On Wed, 2006-03-22 at 23:36 -0800, Steve Langasek wrote: > > On Wed, Mar 22, 2006 at 11:56:23PM +0100, Laszlo Boszormenyi wrote: > > > Do you have any pointers how to do it? I may hack on it, but I know > > > nothing about this. It is #338302 by the way.
> > By editing the .pc (or .pc.in) file in the source package?
> I'm not that beginner. :-) So my question is that it contains a macro
> (@NEON_LIBS@), substituted from configure if I am right.
> So should I just rename Libs to Libs.private? But at least for me it
> seems that Libs should contain "-L${libdir} -lneon @NEON_LTLIBS@" and
> Libs.private should be "@NEON_LIBS@", right?
> With this, the result would be:
> Libs: -L${libdir} -lneon
> Libs.private: -lz -lssl -lcrypto -L/usr/lib -O2 -g -lgssapi_krb5 -lkrb5
> -lk5crypto -lkrb5support -lcom_err -lresolv -lxml2 -lz -lm
Yes, this latter pairing would be the correct one. You still need -lneon in
"Libs", of course, but the rest should be moved to Libs.private since
they're only needed for static linking.
> I miss -O2 and -g from Libs, but otherwise it may be right.
Actually, -O2 and -g have no business being listed in this file at all,
since they are not related to library dependencies -- neon shouldn't be
enforcing compiler optimization flags on other software linking against
neon. But that's a fairly minor bug, since they also shouldn't have any
*effect* at the linking stage... Anyway, don't worry about them not being
listed in Libs:, and only worry about removing them from Libs.private: if
you want to.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
