in reply to Re^8: Perl_croak_xs_usage problem
in thread Perl_croak_xs_usage problem

Somewhere on your system you have two different files called perl510.dll. The one installed with the AS distribution; and the one that doesn't export the Perl_croak_xs_usage entrypoint.

When you revert to the earlier perl installation and things work, it is because the "other perl510.dll" is still being found, but it now matches the one from the earlier perl distribution, so everything works. What you need to do, if you wish to upgrade to the latest version of Perl, is isolate where that hidden dll is located.

My guess is that when you are trying to package whatever it is you are trying to package, it has a dependency upon something that is already packaged--and was packaged using the earlier distribution.

In order to upgrade, you need to repackage that dependency (and any prepackaged dependencies it might have), before you will be able to package anything that has that currently down-level package as a dependency,

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

Replies are listed 'Best First'.
Re^10: Perl_croak_xs_usage problem
by markuhs (Scribe) on Oct 02, 2009 at 10:36 UTC
    BrowserUk, Thanks a lot for your continued help!

    If I search perl*.dll on my local drives, all I find is located in C:\Perl\bin\:
    • perl510.dll
    • perlEx30.dll
    • PerlEz.dll
    • perlis.dll
    • PerlMsg.dll
    • PerlSE.dll
    I doubt, that code from a network drive will be used. In addition my PATH has no drive letter except for C:\... in it.

    So I doubt that any "other DLL" exists...
[reply]

      Your problem is that PAR wraps up all the files into the single .par file; which is essentially a .zip file. From the PAR documentation:

      This module lets you use special zip files, called Perl Archives, as libraries from which Perl modules can be loaded. ... A .par file is mostly a zip of the blib/ directory after the build process of a CPAN distribution

      So, a simply search of your file system will not look inside any .par file dependancies. You would need to use some kind of .zip browser or unzip utility to look inside them.

      As a crude test, you might try: 

      findstr /s /m perl510.dll c:\*.par

      [download]

      Note:That will not be fast. But it should give you a list of .par files that contain a reference to the errent dll.

      So I doubt that any "other DLL" exists...

      They must. Or you OS is lying to you.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]

      A slightly more targetted approach if you have unzip.exe: 

      for /r c:\ %p in (*.par) do @echo %p && unzip -l "%p" | find "perl510.
+dll"

      [download]

      That should give you a list of the .par files on your system along with any that contain the errent dll.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]
        Both lists were empty! There exists no .par file on my C and D drives!
        Syntax is correct though, I created an empty par file and it was found...
[reply]
Re^10: Perl_croak_xs_usage problem
by markuhs (Scribe) on Oct 02, 2009 at 10:40 UTC
    As to your second suggestion:
    What could be already packaged with a wrong version?
    • My own code? - No, it is all plain text files.
    • Any modules? - How can I find out if any?
    • What else???
[reply]

In Section Seekers of Perl Wisdom