Writing Makefile for Digest::MD5 Makefile out-of-date with respect to Makefile.PL Cleaning current config before rebuilding Makefile... /usr/bin/make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true /usr/local/bin/perl Makefile.PL Perl's config says that U32 access must be aligned. Checking if your kit is complete... Looks good Writing Makefile for Digest::MD5 ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false make: *** Makefile Error 1 /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install make had returned bad status, install seems impossible
root@ss_development:~/.cpan/build/Digest-MD5-2.36# perl Makefile.PL Perl's config says that U32 access must be aligned. Writing Makefile for Digest::MD5 root@ss_development:~/.cpan/build/Digest-MD5-2.36# make Makefile out-of-date with respect to Makefile.PL Cleaning current config before rebuilding Makefile... make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true /usr/local/bin/perl Makefile.PL Perl's config says that U32 access must be aligned. Checking if your kit is complete... Looks good Writing Makefile for Digest::MD5 ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false make: *** [Makefile] Error 1 root@ss_development:~/.cpan/build/Digest-MD5-2.36#
Thanks,
Wilmar
Edit: [g0n] - added code tags
I doubt that the MD5 module is causing the particular problem you're having with an apparant "out-of-date" Makefile, but you might consider going into your .cpan/build/ directory, doing rm -rf *MD5* and try the "perl -MCPAN -e shell" again. And this time...
Good luck.
(update: Actually, the cpan page for the MD5 module says that it is "depreciated", but that still amounts to saying "don't use this".)
Why did you install the MD5 module? Did you not notice on the cpan page where it says "The MD5 module is deprecated. Use Digest::MD5 instead."?Because sometimes, people have code that is not within their control that was written when MD5 was not deprecated.
thor
The only easy day was yesterday
According to the output of Makefile.PL, you just need to run make again. But usually, when that does not work, you have a problem with your file systems. For example if you are compiling the module in a directory that is mounted via NFS and the NFS server has a wallclock time different from your client machine. Other problematic filesystems I've heard about are AFS, and maybe your RAID system has a similar problem. You can check that by changing into the build directory and then typing the following:
date touch test.file ls -altr test.file date
The timestamp of test.file should not be in the future (obviously) and it should not be in the past either, but exactly equal to the two outputs of the date command. Of course, you likely won't type in the four commands within one second, but you might either put them into a script or simply notice that the created file has a creation timestamp "too long" ago or "too far" in the future. Neither should happen.
Your system clock is three months in the past. The TAR file is probably newer than that. When it unpacks, the resulting dates are in your 'future', which confuses make.
Fix your system date and your other problems will likely go away.
perlmonks.org content © perlmonks.org and Corion, gordoste, graff, snowhare, thor, willcampos2
prlmnks.org © 2006 edmund von der burg (eccles & toad)
v 0.03