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

1. Download the appropriate Perl version as tarball in your VM
2. Unpack the tarball in your VM:

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

3. 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]

4. Test and install Perl:

   make test
   make install
   [download]

5. Compile your own, hopefully compatible modules for the remote side.