630658 - Cannot compile Windows 64-bit since February 1st

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Armen [:armenzg]]

+++ This bug was initially created as a clone of Bug #626480 +++

The last successful nightly built on the 31st with the following changeset:
http://hg.mozilla.org/mozilla-central/rev/1c6e36066e735a20661126bd0a825bcdd55ec45b
since then it is failing to compile with:

configure: warning: Recreating autoconf.mk with updated nspr-config output
running /bin/sh /e/builds/moz2_slave/cen-win64-ntly/build/js/src/configure  --target=x86_64-pc-mingw32 --host=x86_64-pc-mingw32 --enable-application=browser --enable-update-channel=nightly --enable-update-packaging --enable-jemalloc --enable-debug-symbols --enable-threadsafe --enable-ctypes --with-nspr-cflags='-Ie:/builds/moz2_slave/cen-win64-ntly/build/obj-firefox/dist/include/nspr' --with-nspr-libs='e:/builds/moz2_slave/cen-win64-ntly/build/obj-firefox/dist/lib/nspr4.lib e:/builds/moz2_slave/cen-win64-ntly/build/obj-firefox/dist/lib/plc4.lib e:/builds/moz2_slave/cen-win64-ntly/build/obj-firefox/dist/lib/plds4.lib ' --with-dist-dir=../../dist --prefix=e:/builds/moz2_slave/cen-win64-ntly/build/obj-firefox/dist --with-sync-build-files=/e/builds/moz2_slave/cen-win64-ntly/build --enable-jemalloc --cache-file=../.././config.cache --srcdir=/e/builds/moz2_slave/cen-win64-ntly/build/js/src
loading cache ../.././config.cache
checking host system type... x86_64-pc-mingw32
checking target system type... x86_64-pc-mingw32
checking build system type... x86_64-pc-mingw32
checking for mawk... (cached) gawk
checking for perl5... (cached) /bin/perl
checking for gcc... (cached) cl
checking whether the C compiler (cl  ) works... yes
checking whether the C compiler (cl  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) no
checking whether cl accepts -g... (cached) no
checking for c++... (cached) cl
checking whether the C++ compiler (cl  ) works... no
*** Fix above errors and then restart with               "make -f client.mk build"
make[2]: Leaving directory `/e/builds/moz2_slave/cen-win64-ntly/build'
make[1]: Leaving directory `/e/builds/moz2_slave/cen-win64-ntly/build'
configure: error: installation or configuration problem: C++ compiler cannot create executables.
configure: error: /e/builds/moz2_slave/cen-win64-ntly/build/js/src/configure failed for js/src
make[2]: *** [configure] Error 1
make[1]: *** [obj-firefox/Makefile] Error 2
make: *** [profiledbuild] Error 2
program finished with exit code 2
elapsedTime=57.766000

Comment 1

[Makoto Kato [:m_kato]]

This is rarely issue.   

When rm command by configure is failed, this problem occurs.  This may be mingw32 bug on WOW64.

This will be resolved by "rm -rf objdir" if this occurs.

Comment 2

[Makoto Kato [:m_kato]]

Also, this is on Windows 7 or Windows 2008 R2 only.  Although some forums (such as http://www.sevenforums.com/software/72091-several-minute-delay-when-deleting-any-exe-file.html) talk about this, I don't know good resolution way.

Comment 3

[Armen [:armenzg]]

I am not understanding why would this happen. We have not had this specific issue for few months and now we are hitting it constantly.
Before we build we clobber and after a successful build we clobber as well.

The problem is that after the first successful run we fail and that is because the check for a C++ compiler fails.

I have changed how the system works to reboot after each job.
Let's see if that fixes it.

The interesting thing is that it does the check twice and it fails on the second one:
> checking whether the C++ compiler (cl  ) works... yes

Where could I see the output of 1>&5 ??
> if { (eval echo configure:2280: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
I want to see the output of:
> echo "configure: failed program was:" >&5
which is just before gets set to "no"
> ac_cv_prog_cxx_works=no

This is the diff from a successful build and a failed one:

> @@ -2161,9 +2160,19 @@ checking build system type... x86_64-pc-
> checking for mawk... (cached) gawk
> checking for perl5... (cached) /bin/perl
> checking for gcc... (cached) cl
> checking whether the C compiler (cl  ) works... yes
 checking whether the C compiler (cl  ) is a cross-compiler... no
 checking whether we are using GNU C... (cached) no
 checking whether cl accepts -g... (cached) no
 checking for c++... (cached) cl
-checking whether the C++ compiler (cl  ) works... yes
+checking whether the C++ compiler (cl  ) works... no
+configure: error: installation or configuration problem: C++ compiler cannot create executables.
+configure: error: /e/builds/moz2_slave/cen-win64-ntly/build/js/src/configure failed for js/src
+*** Fix above errors and then restart with               "make -f client.mk build"
+make[2]: Leaving directory `/e/builds/moz2_slave/cen-win64-ntly/build'
+make[1]: Leaving directory `/e/builds/moz2_slave/cen-win64-ntly/build'
+make[2]: *** [configure] Error 1
+make[1]: *** [obj-firefox/Makefile] Error 2
+make: *** [profiledbuild] Error 2
+program finished with exit code 2
+elapsedTime=58.734000

Comment 4

[(not currently active) Ted Mielczarek]

config.log in the objdir should have the full output from failed tests.

Comment 6

[Armen [:armenzg]]

We have been able to build for a long time.

Note sure what we ended up doing to fix this.