> On 24 Aug 2017, at 11:10, David Hodgkinson wrote:
>
> Hi,
>
> I have a little C code that’s bound into mod_perl 1.3, 2005-era code. We’re
> trying to get everything up to date, so 2.0.10 from EPEL it is.
>
> However, this code uses Apache::ExtUtils which no longer
Hi,
I have a little C code that’s bound into mod_perl 1.3, 2005-era code. We’re
trying to get everything up to date, so 2.0.10 from EPEL it is.
However, this code uses Apache::ExtUtils which no longer exists.
Is there a replacement or is binding C code in easier these days?
Thanks,
David
On Mon, Aug 17, 2009 at 7:10 AM, Svip wrote:
> I am trying to install Slash (the same software that runs
> Slashdot.org), which is written in Perl and uses mod_perl for its
> integration with Apache.
>
> Unfortunately, it uses a module called "Apache::ExtUtils", and afte
I am trying to install Slash (the same software that runs
Slashdot.org), which is written in Perl and uses mod_perl for its
integration with Apache.
Unfortunately, it uses a module called "Apache::ExtUtils", and after
some research, I have discovered that this is only available for
mo
All,
When building mod_perl 1.29 on Solaris 9 via apxs, the apaci/perl_config
script returns the value 'cc' as the linker because Apache::ExtUtils calls
basename on the value contained in $Config{ld}, which in my case is
/usr/local/opt/SUNWspro/bin/cc. Truncating this to just '
