Sisyphus wrote:
----- Original Message -----
From: "Robert May"
.
.
A series of tests:
Drop - ok
DropF - fails
AropF - fails
DropFi - fails
DropFile - fails
DropFiles - fails
DropX - fails
DropFx - fails
DropFilesx - fails
xDropFiles - ok
Win32::DropF - fails
Win32::xDropF - ok
Appears to indicate that any module whose last component name starts
with 'DropF' fails.
Except that you've stated that 'AropF' fails and 'DropX' fails. Or did you
mean to write that they are ok ?
Careless on my part. AropF and DropX were OK.
Off to find a mingw forum/list.
You'll find MinGW mailing list subscription details at www.mingw.org
(somewhere). But it's hard to expect helpful answers from them because of
all the perl stuff that's involved in your test case. Better if you could
construct a test case that was pure C. But give it a try anyway (even if you
can't construct a pure C test case) - 'DropF' might mean something to
someone there.
You could just try updating your gcc-3.4.4 and also updating your
mingw32-w32api (assuming your current version is not the latest). My feeling
is that even if you do get an explanation (and I'm sceptical about that),
the solution will be to simply update anyway.
We've crossed messages - after reading the posting guidelines I upgraded
to the latest 'candidate' releases (I was on the leading stable
releases), and my problems went away.
Thanks again,
Rob.(M)
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
