author Mike Hommey <>
Thu, 30 Oct 2014 14:35:01 +0900
changeset 231090 a10056253b8c0e53addd916568a614eeca4d9e81
parent 40458 1584ba8c1b86f9c4de5ccda5241cef36e80f042c
permissions -rw-r--r--
Bug 1091118 - Part 2: Do not use the top-level cache file for freetype2 subconfigure. r=gps, a=lmandel We modify the environment before running freetype2 configure. When it uses the same cache file, it stores knowledge about that environment in the cache file. The cache file is then reused to configure in js/src, with yet again a different environment, which makes clear the cache because of the differences. The configure in js/src is however invoked with the same environment as the main configure was invoked with (mostly), so without freetype2 on the way, reusing the cache for it works as expected. In fact, it works better with the cache because of things coming from mozconfig that are not exported. With freetype2 on the way, as mentioned above, the cache is cleared. Without the cache, js/src/configure does new detections with a possibly different environment, and stores that in the cache. Until the next build, which then uses that different cache for the top-level configure. This results in subtle differences in the HOST_CC/HOST_CXX variables on android builds because those variables are not exported from mozconfig, depending on PATH, what the builder was building before, and if the build is a clobber. Avoiding the freetype2 subconfigure writing its environment variables change to the top-level cache makes the cache never invalidate for js/src.

Please see the file toolkit/content/license.html for the copyright licensing
conditions attached to this codebase, including copies of the licenses

You are not granted rights or licenses to the trademarks of the
Mozilla Foundation or any party, including without limitation the
Firefox name or logo.

For more information, see: