RE: "Case mismatch between module and file name"

On Mon, 15 Sep 2008, Peter T Cash wrote:

Hi Peter,

> I just attempted to make a Windows executable with the ActiveState PerlApp
> tool from a Perl program that I'm developing on a Win 2K box, and got a
> bunch of error messages that contain the phrase in the subject line. The
> program uses Perl/Tk. It runs without complaint from the command line
> interpreter, even when I put in a "use Win32::StrictFileNames 'warn';"
> statement. I checked several of the alleged case mismatches, and can't
> figure out what Active State is complaining about.

Your question is off-topic for the Perl-XML mailing list; please send any
further replies to the PDK mailing list instead!

You are using PDK 6.0.0, which is a very old version that may have various
quirks in its "case mismatch" detection.  You should upgrade at least to
6.0.2, if you are experiencing problems.

Some cases of bogus case-mismatches have been triggered by things like:

* Having PERL5LIB/PERLLIB include the default @INC libraries again

* Using different case for either the driver letter, or the path component
  of the names in PERL5LIB/PERLLIB and paths specified in Config.pm.

> All the file names seem
> to use the correct case. The executable that is created does not run--it
> dies with a message that says: '...instruction at "0x...." referenced
> memory at "0x... The memory could not be read...".

This one doesn't sound like it is related to the case-mismatch problem;
you are seeing an access violation.
 
> Please, can someone help me with this? Is it a question, perhaps, of
> having mismatched Perl/Tk components? If so, what should I download--or
> get rid of?  I'm leery of starting to mess with my Perl environment
> without knowing what's wrong...especially in the middle of a project. Here
> is the output of a query about what Tk components are installed locally:

I understand the resistance to changing the environment, but ActivePerl
5.8.6.811 is also quite old, so your problems may also be solved by moving
to a more recent Perl release.

Cheers,
-Jan

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs