Re: Statically linking against bundled libagg

2008-08-04 Thread Dominic Hargreaves
On Mon, Aug 04, 2008 at 01:42:47AM +0200, Rene Engelhard wrote: > You want -fPIC, both for your lib and agg. Try -lagg_pic if it exists > (when I maintained agg I created it - OOo once used agg too and still > has agg 2.4 in the code - unused by distros, though) Ah, that's the clue that I needed

Re: Statically linking against bundled libagg

2008-08-03 Thread Russ Allbery
Dominic Hargreaves <[EMAIL PROTECTED]> writes: > Building and rudimentary testing against the agg 2.5 shipped with > unstable works, however I have a couple of concerns which make me > reluctant to change the build: > > When building against system agg, I get the lintian error: > > E: libmapnik0.5

Re: Statically linking against bundled libagg

2008-08-03 Thread Rene Engelhard
Hi, Dominic Hargreaves wrote: > When building against system agg, I get the lintian error: > > E: libmapnik0.5: shlib-with-non-pic-code usr/lib/libmapnik.so.0.5.0 > > this does not occur when compiling mapnik's own agg library. > I'm not sure what's happening here; does it indicate a mistake in

Statically linking against bundled libagg

2008-08-03 Thread Dominic Hargreaves
The upstream for my package mapnik builds against an embedded copy of agg, basically an unmodified agg 2.4. I am aware that this is an undesirable situation and would like to try and fix this. As far as I can tell from upstream, the decision to bundle AGG is only a convenience for building on syst