Shared Object Libraries non-PIC

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Shared Object Libraries non-PIC

L505
How does the calling program know that it's not PIC (position independant code)?

i.e. how would you stop a calling program from thinking so? Is it based on what
directory you put the file in?

How do you force a linux program to call a new .SO copy per each process.


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: Shared Object Libraries non-PIC

Jonas Maebe

On 17 Jul 2005, at 01:34, L505 wrote:

> How does the calling program know that it's not PIC (position  
> independant code)?

The linker can find this out while loading the dynamic library (if  
there are relocation entries in text sections, then it's no PIC). You  
should not have to do anything special yourself.


Jonas

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal