On Sat, Feb 21, 2015 at 5:14 AM, Hugo van der Sanden via RT <perlbug-followup@perl.org> wrote: > On Fri Feb 20 07:52:06 2015, hv wrote: >> I think what's there now is worth some smoke-testing, I've renamed the >> branch to smoke-me/hv-grok. > > Hmm, I'm getting a consistent failure for +threads -debugging under win32 that I don't understand. The log for that config (at http://m-l.org/~perl/smoke/perl/win32/smoke-me/Hugo%20van%20der%20Sanden/log564cba32cbcca439aa4cff6c9da609586124b2f3.log.gz) starts like so: > > Configuration: -Dusedevel -Duseithreads > ------------------------------------------------------------------------------ > make distclean ... > Copy Policy.sh ... > Configure ...[./Configure -Dusedevel -Duseithreads -DCCTYPE=MSVC] > > make ...[nmake -f smoke.mk -nologo /D CCTYPE=MSVC80FREE MAKE="nmake -nologo /D" ] > Could Not Find D:\smoke\perl\smoke-me\build\win32\config.h > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\cl.EXE"' : return code '0x2' > Stop. I can't reproduce that just doing a straight build of the branch on Windows 7 with CCTYPE=MSVC110 so it must have something to do with what gets written to smoke.mk by Test::Smoke. I think normally config.h is just copied from a template to build miniperl and then another config.h is generated later to build perl, but it looks like Test::Smoke generates config.h from the outset. Seeing the rules in smoke.mk for generating config.h might shed light on something.Thread Previous | Thread Next