[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Statically linking against bundled libagg

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 to answer my main point. Thanks!

On Sun, Aug 03, 2008 at 04:46:55PM -0700, Russ Allbery wrote:

> It looks like libagg is only available as a static library and not as a
> shared library?  If so, to link it into a shared library, it must be built
> position-independent (-fPIC) on almost every platform except i386.  This
> error message, if libagg isn't PIC on any architecture, will likely result
> in FTBFS on many architectures, such as amd64.
> Ideally, libagg should provide a shared library.  Otherwise, any package
> that links against the existing library would require a rebuild for any
> security vulnerabilities in the library.
> Policy 10.2 covers this somewhat.

There seems to be some discussion of why no shared library is built in


Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

Reply to: