http://qs321.pair.com?node_id=1200907


in reply to Re^2: DBD::ODBC install can't find boot_DBI
in thread DBD::ODBC install can't find boot_DBI

I see the newer strawberry use .xs.dll :/ but ActiveState uses MinGW just like strawberry, as you can see from the full build log

? What do you get with  grep -r boot_DBI .

? What is the difference in the "same compile" between the successful install and failed install ? ( diff the build logs )

Replies are listed 'Best First'.
Re^4: DBD::ODBC install can't find boot_DBI
by DanEllison (Scribe) on Oct 09, 2017 at 14:33 UTC

    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]
    on both machines.

    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.

[reply]
[d/l]
      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?
[reply]
        Both machines return C:\Windows\system32\cmd.exe.
[reply]

      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

[reply]

In Section Seekers of Perl Wisdom