Re^8: Installing (lotsa) modules

Well, it is possible, in theory, if you cross-compile the modules on Windows for the target Linux. But it is very unlikely, and a lot of work, compared to trying to build a Perl similar to the unidentified Linux machine in a VM.

To do that, I would run perl -V (or perl -MConfig -MData::Dumper -e 'print Dumper \%Config', or the mod_perl equivalent), to get at the configure line (config_args), and then potentially look at the integer and float sizes (ivsize, nvsize).

use 5.012;
use Config;

say $Config{config_args};
say $Config{nvsize};
say $Config{ivsize};
[download]

Building a Perl with parameters identical to these (or even one where the whole of Config_heavy.pl matches the one on the unidentified Linux VM) is likely to yield compatible modules you can just upload.

Ideally, I will be merely

Download the appropriate Perl version as tarball in your VM

Unpack the tarball in your VM:

        tar xjf perl-5.32.1.tar.xz
[download]

Configure Perl. Maybe you can find a leftover Policy.sh or config.sh in the unnamed Linux server. Otherwise start with the output of perl -MConfig -e 'print $Config{config_args}' (from the unnamed Linux machine). Try different things until you get the generated Config_heavy.pl to match up with the one from tne unnamed Linux machine.
```
sh Configure ...
[download]
```
Test and install Perl:
```
make test
make install
[download]
```
Compile your own, hopefully compatible modules for the remote side.

Comment on Re^8: Installing (lotsa) modules Select or Download Code

Replies are listed 'Best First'.
Re^9: Installing (lotsa) modules by Bod (Parson) on Mar 27, 2021 at 11:26 UTC
`Perl -V` Read more... (11 kB) Update: config_args -des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexception +s -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-swi +tches -m64 -mtune=generic -Dccdlflags=-Wl,--enable-new-dtags -Dlddl +flags=-shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions + -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-swit +ches -m64 -mtune=generic -Wl,-z,relro -DDEBUGGING=-g -Dversion=5.1 +6.3 -Dmyhostname=localhost -Dperladmin=root@localhost -Dcc=gcc -Dcf_b +y=Red Hat, Inc. -Dprefix=/usr -Dvendorprefix=/usr -Dsiteprefix=/usr/l +ocal -Dsitelib=/usr/local/share/perl5 -Dsitearch=/usr/local/lib64/per +l5 -Dprivlib=/usr/share/perl5 -Dvendorlib=/usr/share/perl5/vendor_per +l -Darchlib=/usr/lib64/perl5 -Dvendorarch=/usr/lib64/perl5/vendor_per +l -Darchname=x86_64-linux-thread-multi -Dlibpth=/usr/local/lib64 /lib +64 /usr/lib64 -Duseshrplib -Dusethreads -Duseithreads -Dusedtrace=/us +r/bin/dtrace -Duselargefiles -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdb +m -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl +=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_getho +stent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endpr +otoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_set +servent_r_proto -Dscriptdir=/usr/bin -Dusesitecustomize nvsize = 8 ivsize = 8 [download]	[reply] [d/l] [select]
Re^10: Installing (lotsa) modules by Corion (Patriarch) on Mar 27, 2021 at 22:14 UTC
Cool - so now you should be able to build a (Linux) Perl that is identically configured as your target Perl. Then you can use your local Perl to compile modules for your remote Perl, as I described in my original reply.	[reply]
Re^11: Installing (lotsa) modules by Bod (Parson) on Mar 27, 2021 at 23:38 UTC
Cool - so now you should be able to build a (Linux) Perl that is identically configured as your target Perl. It seems you have more faith in my abilities than I do!!! As haukex suggested over here - Re^5: Installing PadWalker - I will start a new ~~thread~~ node once I have gathered together the various bits of information into one place. Then I shall be giving it a go. Although I reckon the time has definitely arrived to get a VPS, building a Linux Perl that is configured in a specific way must be a good learning experience.	[reply]