title: Staticly linked library default entry points
body: <p>When linking a static lib, can there be a default entry point for that specific library?</p>
  
  <p>I don't think there is, but would like clarification. We need to add an entry point, during linking, for a static library to initiate some initialisation/verification calls.</p>
  
  <p>For example, we have a static library, libstuff.a, and want to be able to call an initStuff() routine within that library, but during load time (or as close to as possible), not runtime as such (I know it's technically runtime, but out of control of any post _start()/main() routine).</p>
  
  <p><em>To clarify, this was an attempt to fulfill the needs of the NIST FIPS 140.2 spec, specifically section 9.10 of the <a href="http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf" rel="nofollow">Implementation Guide</a>. This includes data and text segment signature verification (see section 9.10's note 3).</em></p>