Does anybody have any idea what could cause this? It's impossible for
the DLL not to define INFINITE. It's no longer a conditional
compilation; if INFINITE is not defined, the code won't compile.
The only thing I can think of is that $! isn't getting set properly, but
I don't know how that c
- Original Message -
From: "Christopher J. Madsen" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 16, 2008 5:22 PM
Subject: Win32-IPC-1.06 fails to define INFINITE
Does anybody have any idea what could cause this?
Beats me - I can't reproduce the problem on a variety of perl build
- Original Message -
From: "Sisyphus" <[EMAIL PROTECTED]>
.
.
or a bug in ExtUtils::CBuilder (which is my hunch)
.
.
Yep, I think Iwas right - downgrading from ExtUtils::CBuilder-0.22 (which
failed its test suite, and should therefore have not been installed in the
first place) to
On Wed, 16 Apr 2008, Christopher J. Madsen wrote:
>
> Does anybody have any idea what could cause this? It's impossible for
> the DLL not to define INFINITE. It's no longer a conditional
> compilation; if INFINITE is not defined, the code won't compile.
>
> The only thing I can think of is that
On Wed, 16 Apr 2008, Jan Dubois wrote:
> | Now that I'm typing this, I have one other idea though: if the module
> | links against a different runtime library than perl58.dll, then the
Just to be clear, what I mean is that IPC.dll links against e.g. MSVCR71.dll
while perl58.dll links against MSVCR
