Here's a patch for Inline.pm that solved it for me, but I'm not too sure
it's the
correct way to go about this. Maybe it would be better to just call
$o->check_config_file
higher up in the glue function...

I don't know if the 'config' file is supposed to always be there in this
situation.


455,459c455
<     # Read the language settings
<     $o->check_config_file ;
<
<     # my $suffix = $Config{dlext};
<       my $suffix = $o->{INLINE}{ILSM_suffix} ;
---
>     my $suffix = $Config{dlext};
471,477c467,470
<     # This was most certainly a bug
<     # $o->{install_lib} = $realpath;
<     $o->{API}{install_lib} = $realpath;
<     # These are now set properly by the $o->check_config_file call above
<     # $o->{INLINE}{ILSM_type} = 'compiled';
<     # $o->{INLINE}{ILSM_module} = 'Inline::C';
<     # $o->{INLINE}{ILSM_suffix} = $suffix;
---
>     $o->{install_lib} = $realpath;
>     $o->{INLINE}{ILSM_type} = 'compiled';
>     $o->{INLINE}{ILSM_module} = 'Inline::C';
>     $o->{INLINE}{ILSM_suffix} = $suffix;
609,610c602,603
< # 1;
< # __END__
---
> 1;
> __END__
889,890c882,883
<     # croak M64_install_not_c($o->{API}{language_id})
<     #  unless uc($o->{API}{language_id}) =~ /^(C|CPP)$/ ;
---
>     croak M64_install_not_c($o->{API}{language_id})
>       unless uc($o->{API}{language_id}) =~ /^(C|CPP)$/ ;

The 3rd part:
609,610c602,603
< # 1;
< # __END__
---
> 1;
> __END__
is only needed to prevent autoloading if you make your changes in place and
do not
reinstall the module, but I'm no autoloading expert.

This worked for me and allowed me to create, make, make test, make install
and use a small
module I made using Inline::Java 0.41 (no changes to Inline::Java where
necessary).
I didn't try installing it on another machine though...


Patrick

---------------------
Patrick LeBoutillier
Laval, Quebec, Canada
----- Original Message -----
From: "Phil Crow" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 28, 2003 10:49 AM
Subject: CPAN build for Inline::Java


> I'm trying to build a module based on Inline::Java.  I
> would like to be able to package it for CPAN.  When I
> tried to build it using Inline::MakeMaker, I received
> the following error during make:
>
> Invalid attempt to install an Inline module using the
> 'Java' language.
>
> Is there any current plan to allow other languages to
> be built into proper CPAN modules?  Could you give me
> pointers so I could help make this happen?  If not,
> could  you suggest a work around?
>
> The purpose of my module is to allow Perl scripts to
> compile Java programs without having to launch a new
> Java virtural machine for each compile request.
>
> Thanks for your help,
>
> Phil Crow
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>

Reply via email to