I get:

Binary file ./blib/arch/auto/DBI/DBI.xs.dll matches
./DBI.c:XS_EXTERNAL(boot_DBI); /* prototype to pass -Wmissing-prototyp
+es */
./DBI.c:XS_EXTERNAL(boot_DBI)
./DBI.def:  boot_DBI
Binary file ./DBI.o matches
Binary file ./dll.exp matches
[download]

The two machines extract the files and compile in a different order, but it appears to be the same files and same compile commands. The only difference I see before the failed test is that one machine refers to dmake as C:\STRAWB~1\c\bin\dmake.exe, while the other refers to it as C:\Strawberry\c\bin\dmake.EXE.

The only difference I see before the failed test is that one machine refers to dmake as C:\STRAWB~1\c\bin\dmake.exe, while the other refers to it as C:\Strawberry\c\bin\dmake.EXE.

This looks like one is using CMD.EXE and the other COMMAND.COM - what are the values of the COMSPEC environment variable?

Both machines return C:\Windows\system32\cmd.exe.

The two machines extract the files and compile in a different order, but it appears to be the same files and same compile commands. The only difference I see before the failed test is that one machine refers to dmake as C:\STRAWB~1\c\bin\dmake.exe, while the other refers to it as C:\Strawberry\c\bin\dmake.EXE.

Hi,

A shortpath versus a longpath wouldn't/shouldn't make a difference if they're pointing to the same place

Yeah "appears to be" sounds very much like "doesn't work" ( vague) but

its windows, a debugger might provide more info

If it works on your version of windows (probably doesn't), try depends.exe Ctrl+O perl.exe , F7 ...foo.pl to see a LoadLibrary trace, might have more info

or from commandline depends.exe /c /f:1 /pb /ot:temp.txt ...perl.exe foo.pl

Or try the same thing (windbg) with WinDbg