in reply to dll not embedded in PAR::Packer's output

Can't load 'C:\Users\Jo\AppData\Local\Temp\par-4a6f\temp-2432\nmtRPcuQp9.xs.dll'

I would run:

objdump -x C:\Users\Jo\AppData\Local\Temp\par-4a6f\temp-2432\nmtRPcuQp9.xs.dll | grep "DLL Name"

That will list the names of all of the dlls that particular dll wants to load.
Obviously it relies on the presence of "objdump.exe" (which ships with Strawberry) and "grep.exe" (which does *not* ship with Strawberry, but is available from here).

Cheers,
Rob
  • Comment on Re: dll not embedded in PAR::Packer's output

Replies are listed 'Best First'.
Re^2: dll not embedded in PAR::Packer's output
by jowe (Sexton) on Nov 28, 2015 at 15:31 UTC
    Thank you guys for your help. Question: Are your suggestions workarounds or is this the way pp is supposed to work?

    Thanks again - Jo

[reply]
      Are your suggestions workarounds or is this the way pp is supposed to work?

      Ideally, pp would pack all of the needed dlls except, I guess, for the Windows system dlls.
      Unfortunately, it can sometimes miss one or more dlls that need to be packed in.

      When that happens you need to firstly identify, and then explicitly include, those dlls.
      I think it's safe to leave out missing Windows system dlls, as the ones on the destination machine should load ok.

      If the "destination" machine is the machine that built the executable, then the executable should run ok (without any need to pack in the missing dlls) if the path includes the location of those "missing" dlls.

      Cheers,
      Rob
[reply]
        um, yeah, wrote this a while ago, ... not convinced its worth pursuing
        Read more... (59 kB)
[reply]
[d/l]

In Section Seekers of Perl Wisdom