Mailing List Archive

> Hello,
> I am trying to use Apache::DBI module. I got it installed on the SUSE
> Linux 11SP4 on my dev box.
>
> It has a dependency of mod_perl2. But when I try to install
> mod_perl2, I get
>
> Please repair your Module::CoreList at lib/Apache2/Build.pm line 51.
> BEGIN failed--compilation aborted at lib/Apache2/Build.pm line 66.
> Compilation failed in require at Makefile.PL line 39.
> BEGIN failed--compilation aborted at Makefile.PL line 39.
>
> Going by the code in Build.pm, I think the version between Corelist
> and Embed is not matching. But the same is installed on our test
> servers and I am not sure what is different. Probably it has
> Apache::DBI for Apache 1.x installed? How do I check? and any help to
> resolve the above error?

You will probably find that maintaining your own copy of Perl is
less work than depending on the pre-compiled [mess] in most
distro's is less work. Building Perl takes little enough time: just
install it into /opt/perl/<version> via:

./Configure --prefix=/opt/perl -de;

(you can see examples of building it in some of my talks on
slideshare.net if you like). After that:

cd /opt/perl;
rm *;
ln -fs <version>/* .;

[ -d /opt/bin ] || mkdir /opt/bin;
cd /opt/bin;
ln -fs ../perl/bin/* .;

and add "/opt/bin" to your path. After that "cpan FooBar" will
install any modules you require, probably with less hassle than
working around O/S issues with library versions.

You could spend a week or so banging your head out deciphering
whatever bone-headed assumptions the distro builders made or
just get it right the first time yourself.

The process may look daunting the first time around but after
a while you'll notice it takes only a few of your favorite
beverages a month to maintain and induces far less annoyance...

Enjoy

--
Steven Lembark 3646 Flora Place
Workhorse Computing St. Louis, MO 63110
lembark@wrkhors.com +1 888 359 3508

Thanks. Let me see what I can do.

Appreciate your response.


~ AK.

Sent with ProtonMail Secure Email.

??????? Original Message ???????
On Tuesday, February 11, 2020 7:04 PM, Steven Lembark <lembark@wrkhors.com> wrote:

> > Hello,
> > I am trying to use Apache::DBI module. I got it installed on the SUSE
> > Linux 11SP4 on my dev box.
> > It has a dependency of mod_perl2. But when I try to install
> > mod_perl2, I get
> > Please repair your Module::CoreList at lib/Apache2/Build.pm line 51.
> > BEGIN failed--compilation aborted at lib/Apache2/Build.pm line 66.
> > Compilation failed in require at Makefile.PL line 39.
> > BEGIN failed--compilation aborted at Makefile.PL line 39.
> > Going by the code in Build.pm, I think the version between Corelist
> > and Embed is not matching. But the same is installed on our test
> > servers and I am not sure what is different. Probably it has
> > Apache::DBI for Apache 1.x installed? How do I check? and any help to
> > resolve the above error?
>
> You will probably find that maintaining your own copy of Perl is
> less work than depending on the pre-compiled [mess] in most
> distro's is less work. Building Perl takes little enough time: just
> install it into /opt/perl/<version> via:
>
> ./Configure --prefix=/opt/perl -de;
>
> (you can see examples of building it in some of my talks on
> slideshare.net if you like). After that:
>
> cd /opt/perl;
> rm ;
> ln -fs <version>/ .;
>
> [ -d /opt/bin ] || mkdir /opt/bin;
> cd /opt/bin;
> ln -fs ../perl/bin/* .;
>
> and add "/opt/bin" to your path. After that "cpan FooBar" will
> install any modules you require, probably with less hassle than
> working around O/S issues with library versions.
>
> You could spend a week or so banging your head out deciphering
> whatever bone-headed assumptions the distro builders made or
> just get it right the first time yourself.
>
> The process may look daunting the first time around but after
> a while you'll notice it takes only a few of your favorite
> beverages a month to maintain and induces far less annoyance...
>
> Enjoy
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Steven Lembark 3646 Flora Place
> Workhorse Computing St. Louis, MO 63110
> lembark@wrkhors.com +1 888 359 3508

On Tue, Feb 11, 2020 at 07:04:56PM -0600, Steven Lembark wrote:
>
> > Hello,
> > I am trying to use Apache::DBI module. I got it installed on the SUSE
> > Linux 11SP4 on my dev box.
> >
> > It has a dependency of mod_perl2. But when I try to install
> > mod_perl2, I get
> >
> > Please repair your Module::CoreList at lib/Apache2/Build.pm line 51.
> > BEGIN failed--compilation aborted at lib/Apache2/Build.pm line 66.
> > Compilation failed in require at Makefile.PL line 39.
> > BEGIN failed--compilation aborted at Makefile.PL line 39.
> >
> > Going by the code in Build.pm, I think the version between Corelist
> > and Embed is not matching. But the same is installed on our test
> > servers and I am not sure what is different. Probably it has
> > Apache::DBI for Apache 1.x installed? How do I check? and any help to
> > resolve the above error?
>
> You will probably find that maintaining your own copy of Perl is
> less work than depending on the pre-compiled [mess] in most
> distro's is less work. Building Perl takes little enough time: just
> install it into /opt/perl/<version> via:
>
> ./Configure --prefix=/opt/perl -de;


This is really true and this is really a problem. It would be nice to
get some alternate packages made for the larger distros


>
> (you can see examples of building it in some of my talks on
> slideshare.net if you like). After that:
>
> cd /opt/perl;
> rm *;
> ln -fs <version>/* .;
>
> [ -d /opt/bin ] || mkdir /opt/bin;
> cd /opt/bin;
> ln -fs ../perl/bin/* .;
>
> and add "/opt/bin" to your path. After that "cpan FooBar" will
> install any modules you require, probably with less hassle than
> working around O/S issues with library versions.
>
> You could spend a week or so banging your head out deciphering
> whatever bone-headed assumptions the distro builders made or
> just get it right the first time yourself.
>
> The process may look daunting the first time around but after
> a while you'll notice it takes only a few of your favorite
> beverages a month to maintain and induces far less annoyance...
>
> Enjoy
>
> --
> Steven Lembark 3646 Flora Place
> Workhorse Computing St. Louis, MO 63110
> lembark@wrkhors.com +1 888 359 3508

--
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com

Being so tracked is for FARM ANIMALS and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013

On 12.02.2020 23:01, Ruben Safir wrote:
> On Tue, Feb 11, 2020 at 07:04:56PM -0600, Steven Lembark wrote:
>>
>>> Hello,
>>> I am trying to use Apache::DBI module. I got it installed on the SUSE
>>> Linux 11SP4 on my dev box.
>>>
>>> It has a dependency of mod_perl2. But when I try to install
>>> mod_perl2, I get
>>>
>>> Please repair your Module::CoreList at lib/Apache2/Build.pm line 51.
>>> BEGIN failed--compilation aborted at lib/Apache2/Build.pm line 66.
>>> Compilation failed in require at Makefile.PL line 39.
>>> BEGIN failed--compilation aborted at Makefile.PL line 39.
>>>
>>> Going by the code in Build.pm, I think the version between Corelist
>>> and Embed is not matching. But the same is installed on our test
>>> servers and I am not sure what is different. Probably it has
>>> Apache::DBI for Apache 1.x installed? How do I check? and any help to
>>> resolve the above error?
>>
>> You will probably find that maintaining your own copy of Perl is
>> less work than depending on the pre-compiled [mess] in most
>> distro's is less work. Building Perl takes little enough time: just
>> install it into /opt/perl/<version> via:
>>
>> ./Configure --prefix=/opt/perl -de;
>
>
> This is really true and this is really a problem. It would be nice to
> get some alternate packages made for the larger distros
>

Just a comment here : we have been installing and using mod_perl2 for many years on many
servers with Linux Debian, and installing it using the normal Debian package manager
commands, without any problems that I can recall.

e.g.

root@kunz:~# uname -a
Linux kunz 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64 GNU/Linux

root@kunz:~# apt-cache search mod_perl
[ .. long list, among which ..]

libapache2-mod-perl2 - Integration of perl with the Apache2 web server
libapache2-mod-perl2-dev - Integration of perl with the Apache2 web server - development files
libapache2-mod-perl2-doc - Integration of perl with the Apache2 web server - documentation

root@kunz:~# apt-get install libapache2-mod-perl2
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapache2-mod-perl2 is already the newest version (2.0.10-2+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@kunz:~#

So I guess that your issue above does indeed have to do with the specific SUSE packages,
and you should probably discuss that with them.


>
>>


>> (you can see examples of building it in some of my talks on
>> slideshare.net if you like). After that:
>>
>> cd /opt/perl;
>> rm *;
>> ln -fs <version>/* .;
>>
>> [ -d /opt/bin ] || mkdir /opt/bin;
>> cd /opt/bin;
>> ln -fs ../perl/bin/* .;
>>
>> and add "/opt/bin" to your path. After that "cpan FooBar" will
>> install any modules you require, probably with less hassle than
>> working around O/S issues with library versions.
>>
>> You could spend a week or so banging your head out deciphering
>> whatever bone-headed assumptions the distro builders made or
>> just get it right the first time yourself.
>>
>> The process may look daunting the first time around but after
>> a while you'll notice it takes only a few of your favorite
>> beverages a month to maintain and induces far less annoyance...
>>
>> Enjoy
>>
>> --
>> Steven Lembark 3646 Flora Place
>> Workhorse Computing St. Louis, MO 63110
>> lembark@wrkhors.com +1 888 359 3508
>