Problem with perl on 6.6.7

[drchips]

Greetings to all..

Long-time user of unRAID, started with 4.7, spent a long time on 5.02, recently apgraded to 6.6.7

All spinning drives have been converted to xfs, ssd cache added.
System is running beautifully..

 

On 5.0.2 I had a perl script (self-written) that provided the majority of the final functionality of the current File Integrity plugin - so: File Integrity installed.

 

My problem:
I would like to have my perl environment to be available.
perl installed (perl-5.26.1-x86_64-4.txz) via Nerd Pack plugin and confirmed with perl -v

 

cpan install DBD::SQLite FAILS with message:
'make -- NOT OK'
confirmed make not installed.
Searched Nerd Pack, found in Dev Pack, installed (make-4.2.1-x86_64-3.txz).

 

2nd attempt @ DBD::Sqlite FAILS with message:
'make: error while loading shared libraries: libguile-2.2.so.1:'
Searched Dev Pack, installed (guile-2.2.3-x86_64-2.txz)

 

3rd attempt @ DBD::Sqlite FAILS with message:
'make: error while loading shared libraries: libgc.so.1:'
Searched Dev Pack, installed (gc-7.6.6-x86_64-1.txz)

 

4th attempt @ DBD::Sqlite FAILS with message:
'/bin/sh: cc: command not found'
Searched Dev Pack, installed (gcc-8.2.0-x86_64-1.txz)

 

5th attempt @ DBD::Sqlite FAILS with message:
'cc: error trying to exec 'as': execvp: No such file or directory'
Searched Dev Pack, installed (binutils-2.31.1-x86_64-4.txz)

 

6th attempt @ DBD::Sqlite FAILS with message:
'/usr/libexec/gcc/x86_64-slackware-linux/8.2.0/cc1: error while loading shared libraries: libmpc.so.3: cannot open shared object file: No such file or directory'
Searched Dev Pack, installed (libmpc-1.1.0-x86_64-2.txz)

 

7th attempt @ DBD::Sqlite FAILS with message:
'/usr/lib64/perl5/CORE/perl.h:694:10: fatal error: sys/types.h: No such file or directory'
' #include <sys/types.h>'
'          ^~~~~~~~~~~~~'
Searched Dev Pack, installed (kernel-headers-4.14.37-x86-1.txz)

 

NOW I AM STUCK, as this has not solved the issue..
Googling hints @ libpcap or kernel headers as the solution.....

 

I am obviously missing something, but knowing nowt about Linux, I am stuck..

 

Please can I beg some help.

Cheers...

[hawihoney]

I always have these problems too. All packages that need C header to compile (e.g. DBI) don't work here. And if they work I do get problems with Unraid. I don't start database related Perl scripts in Unraid. I did install a Windows VM to do just that. It's a pain but I never could find the differences in DEVPACK/NERDPACK and what Perl needs to compile. 

[drchips]

Thanks hawihoney,

 

I already have a vm doing that, but what an AWFUL WASTE of resources, when it should be running on unRAID where it can be triggered @ the right time / conditions.

 

I had it running under 5.0.2 (32-bit system, triggered by incron).

 

It just seems 'off' having a linux system that does not support the perl environment.

Could it be a 32-bit / 64-bit thing?

Unlikely! ....

 

Cheers...

[drchips]

Greetings,

 

A shameless bump to beg some assistance.

 

I have created a vm on my Workstation (not unRAID) and loaded Slackware 14.2. (which has a working perl environment)

 

I am hoping to be able to perform some sort of diff with respect to types.h and I have come up with the following candidates:

./usr/include/dns/types.h
./usr/include/bits/types.h
./usr/include/isccc/types.h
./usr/include/isc/types.h
./usr/include/asm-generic/types.h
./usr/include/netlink/types.h
./usr/include/c++/5.3.0/parallel/types.h
./usr/include/sys/types.h
./usr/include/irs/types.h
./usr/include/pci/types.h
./usr/include/asm-x86/types.h
./usr/include/libnl3/netlink/types.h
./usr/include/linux/iio/types.h
./usr/include/linux/types.h
./usr/lib64/bcc/include/asm/types.h
./usr/lib64/bcc/include/generic/types.h
./usr/lib64/bcc/include/sys/types.h
./usr/lib64/bcc/include/arch/types.h
./usr/lib64/bcc/include/linuxmt/types.h
./usr/lib64/bcc/include/msdos/types.h
./usr/lib64/bcc/include/linux/types.h
 

Can anybody throw a few hints my way?

 

Cheers.

[drchips]

Still running the Slackware VM, but looking at creating a docker next...

I think I should be able to strip a docker down to the minimum for a perl environment.

 

I think it is probably whistling in the wind to expect full support for perl to be re-instated now that it has been 'killed'.

 

So, a minimum docker may be the best I can hope for..................

[drchips]

Also, a docker will be easier to carry through the upgrades.