note tsee Wow, 6MB is quite a shared object! By the way, what do you mean by "cannot be shared"? Can't be shared in the concept of shared memory? Does that work if the instances run in separate perl's? If so, I wonder why this doesn't happen if you run the same par'd binary twice because the cache area should be the same. Does it, perhaps, help to put Math::Pari into a separate .par and using that? Try fiddling with the $ENV{PAR_GLOBAL_TEMP} variable to force sharing of the cache directory. And please forgive me for hand-waving. :) On a related note: If you download the PAR-0.970.tar.gz distribution and look for the pare utility in the contrib/ subdirectory, you'll find a tool to remove all common modules from one executable and make it depend on the other. I'm not sure it works for the dependency on a .par. But perhaps pp -X foo.par works by skipping the stuff in foo.par during packaging! If you plan to deploy Math::Pari to the target system(s), you can use a .par as well - if you like. Here, I would advise a slightly different process: <ul> <li>use [cpan://PAR::Dist::FromCPAN]'s cpan2par tool to create a Math-Pari-VERSION-PLATFORM-PERLVERSION.par binary from Math::Pari</li> <li>Ship that to the clients</li> <li>Have them install that binary with <code>perl -MPAR::Dist -einstall_par</code> (assuming only one .par in the current directory. See [cpan://PAR::Dist].)</li> </ul> You can even embed PAR::Dist into a simple "install_par.pl" script since it's pure-perl without non-core dependencies. About your suggestion for the FAQ: Would you mind editing the wiki yourself? Just modify the existing answer or, if you like, create a new Q/A pair. Thanks! Steffen 593384 593514