On Thu, May 23, 2019 at 01:02:59PM +0000, Dudziak Krzysztof wrote: > Thanks for feedback from you. > > > > Isn't it that way for shared libraries IN GENERAL to need be compiled > > > as position-independent code then linked as such ? > > Not in theory. > Ansgar kindly elaborated the point bit more so I can feel the background. Thanks to Ansgar too : ) > Among all cases being constituting pointed statement any one > in active use currently, e.g. because contemporary and good alternative for PIC-concept? I cannot say about all architectures we currently have and may have in the future but I think the only modern way is indeed PIC. > > > In my understanding chapter's text in its current form suggests > > > application of -fPIC thus that one of position-independent code to be of > > > narrower scope than originally. > > That section talks about mandating -fPIC, not about narrowing its scope. > From that one sentence myself gets feedback it was aspiring to make reproduction of > -fPIC description fragments. EPARSE, sorry. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature