On 05/10/02 23:56 +0100, Nicholas Clark wrote:
> On Sat, Oct 05, 2002 at 11:39:02AM -0700, Brian Ingerson wrote:
> 
> > Not good. I tried to reproduce this using my non-first-in-path-perl on a
> > clean install. But it worked fine.
> 
> I think I now know why... :-)
> 
> > Is Foo.pm in the blib tree?? Also try uninstalling any previous Inline
> > installs. I wonder how it found C, but not Foo.
> 
> Tried the uninstal. Didn't work. [Yes, even my bleeding edge 5.9.0 seemed
> to have Inline installed for it. It's like Test::More - it gets everywhere
> :-)]
> 
> But the Foo.pm was interesting. I added a die:
> 
>           next if $mod =~ /^(MakeMaker|denter|messages)$/;
>           eval "require Inline::$mod;\$register=&Inline::${mod}::register";
>           die $@ if $@;
>           next if $@;
> 
> I think that maybe some more diagnostics there in case of unexpected failure
> would be handy in the general case. They immediately grassed up why Foo.pm was
> failing to register.

ok

> 
> > Inline creates the _Inline/config file if one doesn't exist. It polls every
> > Inline::* module it can find and calls the register() method. It should find
> > Inline::Foo in the blib and poll it. I'm perplexed.
> 
> Appended patch cures all problems previous problems, and gets me as far as
> this:

Well, thanks for patch. But I can't imagine what in the world YAML.pm is
needed for. I definitely don't wan't Inline dependent on YAML (at least
not yet ;).

> PERL_DL_NONLAZY=1 /usr/local/bin/perl5.9.0 "-I../../blib/lib" "-I../../blib/arch" 
>test.pl
> 1..1
> Can't locate Inline/C/grammar.pm in @INC (@INC contains: ../../blib/lib 
>../../blib/arch /usr/local/lib/perl5/5.9.0/i386-freebsd /usr/local/lib/perl5/5.9.0 
>/usr/local/lib/perl5/site_perl/5.9.0/i386-freebsd 
>/usr/local/lib/perl5/site_perl/5.9.0 /usr/local/lib/perl5/site_perl .) at test.pl 
>line 3.
> BEGIN failed--compilation aborted at test.pl line 3.
> not ok 1
> *** Error code 2

Yes. I caught and fixed this one while trying to recreate your problem.

Cheers, Brian

Reply via email to