We have a resolution for this. It all turned out to be a side effect of
running out perl interpreter with -M-ops=exit. The reason why we disabled
exit is because we cannot gracefully recover from it if used by customer
scripts. If you have any ideas how to catch "exit" in a different way,
that would be great. Meanwhile, we will conditionally allow "exit" to
exist in order to support Inline.
Thanks for your assistance, and it's really a neat module!
--
cg
On Thu, 31 Oct 2002, Piers Harding wrote:
> Sounds like it is running into the either the Taint checking issue or
> Inline is not bootstraping the module.
> You could try something like:
> require DynaLoader;
> eval { DynaLoader::bootstrap("Yax") };
>
> inside your module to make sure this is happening?
>
> Cheers.
>
>
>
> On Thu, Oct 31, 2002 at 01:59:53AM +0000, Christian Goetze wrote:
> >
> > > Did you try writing it as an Inline *module* (like Math::Simple in the
> > > distro)?
> >
> > If with that you mean using this:
> >
> > use Inline::MakeMaker;
> > # See lib/ExtUtils/MakeMaker.pm for details of how to influence
> > # the contents of the Makefile that is written.
> > WriteInlineMakefile(
> > 'NAME' => 'Yax',
> > 'VERSION_FROM' => 'Yax.pm', # finds $VERSION
> > 'PREREQ_PM' => {}, # e.g., Module::Name => 1.1
> > );
> >
> > and this:
> >
> > package Yax;
> >
> > require 5.005_62;
> > use strict;
> > use warnings;
> >
> > use vars qw($VERSION @ISA @EXPORT);
> > require Exporter;
> > @ISA = qw(Exporter);
> > @EXPORT = qw(); # doesn't seem to be necessary
> > $VERSION = '0.20';
> >
> > use Inline (C => 'DATA',
> > NAME => 'Yax',
> > VERSION => '0.20',
> > MYEXTLIB => '/home/cg/Yax/libyax.a',
> > );
> >
> > 1;
> >
> > __DATA__
> >
> > Then yes, we did build a module. It installed a Yax.so into site_perl and
> > everything you'd expect.
> >
> > Running the embedded perl with strace showed that no attempt was made to
> > load Yax.so, so I'm assuming something is wrong with the loader logic...
> > --
> > cg
>
