On Mon, 07 Mar 2005, Paul Brossier wrote: > On Mon, Mar 07, 2005 at 02:05:44PM +0100, Florian Weimer wrote: > > >> Why do you insist to have that code be position-independant ? > > > I could say because it is a 'must' in the debian policy, but... > > There is no such requirement in the Policy. 8-) > > 10.2. Libraries > --------------- > > The shared version of a library must be compiled with `-fPIC', and the > static version must not be. In other words, each source unit (`*.c', > for example, for C files) will need to be compiled twice. > > hrm, but yeah of course, one could say that it's fine if a > library compiled with -fPIC still contains non position > independant code. :)
Just a small question: does the system KNOW an object compiled with -fPIC but which contains non-PIC code must be treated as a non-PIC object? If it does, then yes, it really should not be a major problem to leave the non-PIC code in place. The lib would not be prelinkable, but that is no major loss. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
