On Tue, Sep 30, 2014 at 7:36 AM, <sisyph...@optusnet.com.au> wrote: > > No. > It should not be possible for the set up you described to result in a > "clash" of XS symbols, no matter how hard you try. The XS symbols are > private to both modules - it doesn't matter if identical symbols exist. >
Thanks for the quick reply, Rob. Just to clarify I was meaning the symbols in the shared third-party .a library. Where two separate Perl (XS) modules link to the same static .a library and those two Perl modules are then used in the same program. We are going to try and get the .a library built as a .so file (or really many .so libraries). As it is right now it's kind of a beast so the resulting Perl XS-build .so files are quite big. Seems like a cleaner approach, and that would allow patching the third-party library w/o having to rebuild the Perl modules. Thanks again. -- Bill Moseley mose...@hank.org
