Hi, On 25.10.2016 13:55, Guillem Jover wrote: > I don't think the reasoning there is sound (as I've mentioned > elsewhere), and the policy bug should be closed. > > Switching from no-PIE to PIE by default preserves our current behavior > WRT static libraries vs shared libraries.
The current policy says: "As to the static libraries, the common case is not to have relocatable code" As of gcc-6 version 6.2.0-7 this is factually wrong, because the compiler enables PIE by default, which means it produces relocatable code. This should definitely be updated to reflect reality. > For many static libraries, > making them embeddable into other shared libraries is really not > desirable. And those should be using the shared libraries instead. If that's the reason why it shouldn't be done, policy should mention it. The current policy does not list this as reason not to use -fPIC, merely: "since there is no benefit" > I still think the current policy is fine, and if someone wants to build > a static library with PIC it should be brought up here. The current ffmpeg packages builds shared and static libraries, the latter because they are used in the test suite. Both are built from the same object files compiled with -fPIC. Do you really think those static libraries should not be included in the binary lib*-dev packages just because they are not incompatible with including in other shared libraries? Best regards, Andreas
