compiler construction - Difference between shareable and non-shareable libraries for linking -


I am currently installing on a cluster. For Configure , a parameter is - enabled - , "MPIH is built when a shared library is created" (page 9). It works as an example only, my question is MPIG is an agnostic: is there any difference between "shareable" and "non-shareable" libraries?

By now I have assumed that a library (static), dynamic, late linking), but

  • Are there different library types?
  • If yes, what's the difference, especially the technical differences? Are non-shareable libraries compiled differently or have less functionality?
  • If not, what about MPEEH installation manual entry?

    Thank you!

    There is a difference between "shareable" and "non-shareable" libraries

    Yes: can be shared between different executions using shared libraries.

    Archive libraries (as opposed to shared) and can be shared only when using multiple instances of that executable, but not between different executives.

    Edit:

    There is a lack of use of shared libraries

    There are several:

    • Calling in the shared library, as well as in the library, calls and access to global data can be a bit slower (usually 1-2%, but can be up to 10% in extreme cases). There are, but they are not trivial.
    • Using shared libraries requires that you target the both main executables, and all shared libraries (and the right of these shared libraries Version) is needed once it reaches the number 100 libraries it can be an important problem.
    • The use of shared libraries opens doors for "" and many odd errors when your shared library of your development system does not match the version versions of your production / cluster / customer system.

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -