For ages now my smokes have been failing with the occasional 'M' status. My life has calmed down enough now for me to investigate this, and it *seems* like having set 'makeopt' to '-j2' causes something to fail.
I was wondering if anyone else has noticed problems with this, or if I'm just crazy? The only evidence I can offer for this is that when -j2 is specified and I see M failures in my report the log file (using 58x as an example) contains a line like Can't locate re.pm in @INC (@INC contains: ../../lib ../../lib /usr/local/lib/perl5/5.8.5/i686-linux-thread-multi-64int-ld /usr/local/lib/perl5/5.8.5 /usr/local/lib/perl5/site_perl/5.8.5/i686-linux-thread-multi-64int-ld /usr/local/lib/perl5/site_perl/5.8.5 /usr/local/lib/perl5/site_perl .) at ../../lib/ExtUtils/xsubpp line 278. for each M failure, and there is only one Can't locate auto/POSIX/autosplit.ix in @INC (@INC contains: ../../lib /usr/local/lib/perl5/5.8.5/i686-linux-stdio /usr/local/lib/perl5/5.8.5 /usr/local/lib/perl5/site_perl/5.8.5/i686-linux-stdio /usr/local/lib/perl5/site_perl/5.8.5 /usr/local/lib/perl5/site_perl .) at ../../lib/AutoLoader.pm line 160. line in the log. If I change the config so that the 'makeopt' => '' then there is a "Can't locate auto/POSIX/autosplit.ix ..." line for each combination of -DDEBUGGING and other flags in the log file. We will see if this fixes the M failure problems over the next few days. I am sorry to have been submitting "noisy" reports for so long. Regards, Mike -- [EMAIL PROTECTED] | The "`Stok' disclaimers" apply. http://www.stok.co.uk/~mike/ | GPG PGP Key 1024D/059913DA | Fingerprint 0570 71CD 6790 7C28 3D60 | 75D2 9EC4 C1C0 0599 13DA
