Bug#351359: libagg-dev: pkg-config --libs return -lagg which is not built with -fPIC and fail to link on amd64 arch.

[cedric <cedric.borgese@gmail.com>]

Le Samedi 4 Février 2006 14:23, vous avez écrit :

Sorry for the late answer but I was quite busy last time...
> Hi,
>
> Cédric wrote:
> > pkg-config --libs libagg should return -lagg_pic on amd64 in stead of
> > -lagg which is not built with -fPIC and fail to link on some others libs
> > (kdelibs4 for instance)
>
> The problem here is that when you want to link agg into a lib/app which
> is static you don't want -lagg_pic but -lagg.

I take a look at the help of pkg-config (pkg-config --help)
and there is the --static option for static linking, so I think --libs assume 
you're linking dynamically with the lib.

>
> No, it should not return -lagg_pic on specific architectures (!i386 to
> be precise) IMHO. But I'll think of it.
>
> Why don't you just spcify -lagg_pic when you know it is needed?
> (Debian-only addition, though, -lagg_pic doesn't exixt upstream, it's
> built in Debian because I know it's needed on !i386, e.g. for OOo, but
> I already patched OOo to use -lagg_pic)

This implies patching all (not that many at the moment...) packages that link 
with libagg. And there is no more utility in a great tool like pkg-config if 
it works on a limited number of arch and libs and you have to patch your 
build system if you dont use the right ones.

>
> Regards,
>
> Rene

Thanks for taking a look at my problem.

cédric.