> > > > Reading DynaLoader.pm line 213 it says that very often programs fail saying > that there's an error in there, but it's really the XS initialization code > for the module which is really failing. Since my XS skills are, well, close > to zero, I can't trace anything there. How can I trace the loading of an XS > module? I have tried even with strace, but I didn't see anything... > > I just worked through an XS loader issue last week. It typically has to do with unsatisfied dependencies in the web of shared libs that you're trying to load.
so find the .so in question, and run ldd on it. ldd will list all of that library's dependencies, and tell you if it can find them or not. If it can't then you probably need to add a few libs to your LD_LIBRARY_PATH variable. Len.
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
