Hi, We can stated that '-fpic' or '-fPIC' is necessary for 'so'-es. The '-fpic' generates a smaller and faster code as it is stated in http://people.redhat.com/drepper/dsohowto.pdf. If the '-fpic' doesn't work for a huge 'so' code it, will be signaled by gcc in its linking time, is not the case on my test distributions. The build time is not so long on my linux systems, so the method proposed by Viktor is plausible [Sorry, I lost this info or I can't realize the interdependencies]. The other proposal is to use '-fpic' or '-fPIC' [-fpic my option] as default and optionally without, is maybe the easiest IMO.
Best regards, István -----Original Message----- From: Tamas TEVESZ [mailto:[email protected]] Sent: 2009. szeptember 11. 17:04 To: Harbour Project Main Developer List. Subject: Re: [Harbour] SELinux alert: libharbour-2.0.0.so which requires text relocation On Fri, 11 Sep 2009, Viktor Szakáts wrote: > Recent changes in GNU Make system makes it possible to > build with -fpic for Harbour dynamic lib and build without > it for static libs/binaries in one build pass. [ of course > the build will take more time to complete as most core libs > will be compiled twice. ] > > I've proposed this option already, but without consent > / interest / and most importantly input from Linux (*nix) > users, I couldn't start on that road. my op is that it should just be on by default, and those who want should be able to switch it off (-fPIC that is). i think that despite speedtst showing what it's showing, it's an incredibly synthetic test (i mean, c'mon, 98+% of the time you'll be waiting for either the user or disk/network/other io, not the cpu), and as such, it is great for checking whether you've just improved the vm or actually made it worse, but i don't believe it to reflect real-world usage at all. -- [-] mkdir /nonexistent _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
