>>> Compiling source in /var/tmp/portage/IO-Socket-SSL-0.97/work/IO-Socket-SSL-0.97 ... * Using ExtUtils::MakeMaker Checking if your kit is complete... Looks good Writing Makefile for IO::Socket::SSL make: Warning: File `/usr/lib64/perl5/5.8.8/x86_64-linux/Config.pm' has modification time 2.9e+04 s in the future Makefile out-of-date with respect to /usr/lib64/perl5/5.8.8/x86_64-linux/Config.pm /usr/lib64/perl5/5.8.8/x86_64-linux/CORE/config.h Cleaning current config before rebuilding Makefile... make -f Makefile.old clean > /dev/null 2>&1 /usr/bin/perl5.8.8 Makefile.PL "INSTALLMAN3DIR=none" "PREFIX=/usr" "INSTALLDIRS=vendor" "DESTDIR=/var/tmp/portage/IO-Socket-SSL-0.97/image/" Checking if your kit is complete... Looks good Writing Makefile for IO::Socket::SSL ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false make: *** [Makefile] Error 1 !!! ERROR: dev-perl/IO-Socket-SSL-0.97 failed. Call stack: ebuild.sh, line 1894: Called dyn_compile ebuild.sh, line 941: Called src_compile ebuild.sh, line 1609: Called perl-module_src_compile !!! compilation failed !!! If you need support, post the topmost build error, and the call stack if relevant. don't know what to do and post... thanx
I've seen this happen when you have /var/tmp/portage mounted (or /var/tmp/ or /var/) on another partition and atime's aren't being set correctly, or when your building it from packages and the build box has a skewed clock. Since you didn't provide emerge info, my best recommendation woul be to find /usr/lib64/perl5 -type f -exec touch {} \; to try and get the last modtime's up to speed. And check your clocks and mount options of course.
I think it's a skewed clock problem... don't know how to fix it but I will ! :)= Thanx
going ahead and closing per last comment :)
