On 09/17/2011 01:35 PM, George Greer wrote:
Smoke logs available at http://m-l.org/~perl/smoke/perl/Automated smoke report for 5.15.2 patch 2a014a4b51424c9ea9e46c78e7b3840cc28e4aaa v5.15.2-462-g2a014a4 zwei: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (GenuineIntel 2668MHz) (x86_64/8 cpu) on linux - 2.6.38-11-generic [debian] using g++ version 4.5.2 smoketime 46 minutes 3 seconds (average 11 minutes 31 seconds) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep v5.15.2-462-g2a014a4 Configuration (common) -Dcc=g++ -O ----------- --------------------------------------------------------- F O F O -Uusenm F O F O -Uusenm -Duseithreads | +--------- -DDEBUGGING +----------- no debugging Locally applied patches: uncommitted-changes SMOKE2a014a4b51424c9ea9e46c78e7b3840cc28e4aaa Testsuite was run only with 'harness' Failures: (common-args) -Dcc=g++ -O [default] -Uusenm [default] -DDEBUGGING -Uusenm [default] -Uusenm -Duseithreads [default] -DDEBUGGING -Uusenm -Duseithreads ../t/porting/podcheck.t.....................................FAILED 181, 494
I can't reproduce this on my linux machine. I've tried two different configurations, the final one being,
./Configure -Dusedevel -des -DDEBUGGING -Uusenm -Duseithreads
