On Mon, Aug 23, 2010 at 09:38:42 (CEST), IOhannes m zmoelnig wrote:

> On 2010-08-23 09:25, IOhannes m zmoelnig wrote:
>> On 2010-08-22 20:06, Jonas Smedegaard wrote:
>> anyhow, i had a look at the debian policy, and it says (in chapter 10.2
>> Libraries on todays http://www.debian.org/doc/debian-policy/ch-files.html):
>> "If the package is architecture: any, then the shared library
>> compilation and linking flags must have -fPIC, or the package shall not
>> build on some of the supported architectures".
> reading on, i also noticed:
> "Shared object files (often .so files) that are not public libraries,
> that is, they are not meant to be linked to by third party executables
> (binaries of other packages), should be installed in subdirectories of
> the /usr/lib directory. Such files are exempt from the rules that govern
> ordinary shared libraries, except that they must not be installed
> executable and should be stripped [A common example are the so-called
> "plug-ins", internal shared objects that are dynamically loaded by
> programs using dlopen(3).]"
> i understand this as the "-fPIC" rule actually doesn't apply at all to
> Pd-externals.

If they are indeed in non-standard paths such that the dynamic linker
doesn't see it without setting LD_LIBRARY_PATH or similar, then you're
right. But..

> nevertheless, it complies with it...

even on amd64? There are some architectures that are pretty picky about
position independent code.  BTW that's why there is this rule in debian
policy in the first place.

Reinhard Tartler, KeyID 945348A4

pkg-multimedia-maintainers mailing list

Reply via email to