Bug#172078: lintian: suggest test for PIC in .a
Niels Thykier <niels@thykier.net> writes:
>
> On 2012-12-20 12:57, Bastien ROUCARIES wrote:
>> control: tags -1 + moreinfo
>>
>> The policy have changed and I could not found the text. Could you give
>> some verbatim copy ?
Oh, I see in the short time since I posted it's moved from 11.2 to 10.2.
I would probably re-word my .desc for clarity now and since the libtool
bug presumably no longer applies unless you're stuck at its 1.4.
10.2. Libraries
---------------
...
As to the static libraries, the common case is not to have relocatable
code, since there is no benefit, unless in specific cases; therefore
the static version must not be compiled with the `-fPIC' flag. Any
exception to this rule should be discussed on the mailing list
_debian-devel@lists.debian.org_, and the reasons for compiling with
the `-fPIC' flag must be recorded in the file `README.Debian'. [3]
...
[3] Some of the reasons for linking static libraries with the `-fPIC' flag
are if, for example, one needs a Perl API for a library that is under
rapid development, and has an unstable API, so shared libraries are
pointless at this phase of the library's development. In that case,
since Perl needs a library with relocatable code, it may make sense to
create a static library with relocatable code. Another reason cited
is if you are distilling various libraries into a common shared
library, like `mklibs' does in the Debian installer project.
--
The sigfile music jargon series:
Classical Music -- the composer is dead.
Classic Rock -- the composer is probably dead.
Reply to: