On Tue, 02 Aug 2011, Erland Sommarskog wrote:
> "Sisyphus" (sisyph...@optusnet.com.au) writes:
> > Jan Dubois possibly has some ideas (and definitely has a better
> > understanding) about this. If he doesn't turn up here, and you wish to get
> > some feedback from him, try posting to the perl-win32-users list hosted by
> > ActiveState - he seems to keep a close eye on that list.
>
> Seems like Jan turns up whenever I ask a Perl question - unless I ask
> it in ActiveStates own forums. This time he is silent, but vacation
> is commonplace this time of year.
Like Cuthulu, I'm always watching, waiting, at the other end of the world... :)
I don't know what may be causing your troubles though. Just playing the
guessing game, the most likely cause of problems with modules compiled
with VS 2005 and later is the fact that Microsoft changed time_t to be
64 bit even in the 32-bit compiler.
To compensate for this we compile 32-bit Perl with the -D_USE_32BIT_TIME_T
compiler option when using VC6 or VC7. This does nothing for those builds
themselves, but keeps this information in the Config{ccflags}. So when an
extension module is compiled with VC8 and later, this option will force
time_t back to 32 bits to remain compatible with the core Perl version.
ExtUtils::MakeMaker, Module::Build, and Module::Install are all supposed to
propagate the ccflags correctly. But if you are doing anything funky in
your Makefile.PL (or whatever you are using), then please make extra sure that
you are not using this setting.
Cheers,
-Jan
