1497949 - Tup build fails with "tup error: Explicitly named file 'jccolor-sse2-64.asm' not found in subdir 'refactoring/media/libjpeg/simd'"

Status: RESOLVED DUPLICATE of bug 1499156

(Firefox Build System :: General, defect)

Description

[Botond Ballo [:botond]]

After pulling and trying to rebuild today, my tup build is giving me the following error:

 0:59.55 [ tup ] [13.976s] Reading in new environment variables...
 0:59.57 [ tup ] [13.997s] Parsing Tupfiles...
 0:59.57  ~ 0% 2738) [0.000s] eclipse_refactoring-desktop-clang/.metadata
 0:59.57  ~ 0% 2737) [0.000s] eclipse_refactoring-desktop-clang/.metadata/.plugins/org.eclipse.core.resources
 0:59.57  ~ 0% 2736) [0.000s] eclipse_refactoring-desktop-clang/.metadata/.plugins/org.eclipse.core.resources/.root
 0:59.57  ~ 0% 2735) [0.001s] refactoring/media/libjpeg
 0:59.57  ~ 0% 2734) [0.000s] refactoring/media/libjpeg/simd
 0:59.57 * ~ 0% 2733) [0.001s] out-of-tree-objdirs/refactoring-desktop-clang/media/libjpeg
 0:59.57 tup error: Explicitly named file 'jccolor-sse2-64.asm' not found in subdir 'refactoring/media/libjpeg/simd'
 0:59.57 tup error: Error parsing Tupfile line 7
 0:59.57   Line was: ': /home/botond/dev/mozilla/refactoring/media/libjpeg/simd/jccolor-sse2-64.asm | $(MOZ_OBJ_ROOT)/<installed-files> |> ^ AS %f...'
 0:59.57  *** tup: 1 job failed.
 0:59.64 780 compiler warnings present.
 0:59.74 ccache (direct) hit rate: 2.7%; (preprocessed) hit rate: 6.1%; miss rate: 91.2%

The directory in question is in a _different_ source directory than the one I'm trying to build...

Comment 1

[Chris Manchester (limited bugmail, email directly)]

This looks like the case of out-of-date Tupfiles in an objdir other than the active objdir failing the build... tup will parse all the Tupfiles it sees and do some checks, so when pulling this is a pretty common hazard. The workaround is to activate the failing objdir in your mozconfig and run |./mach configure| before proceeding.

Comment 2

[Kim Moir [:kmoir] ET]

Triaging - Chris is this something that could be covered in the documentation or should there be an error message?

Comment 3

[Chris Manchester (limited bugmail, email directly)]

The current docs mention this, but incorporating the workaround into people's workflows isn't ideal. I don't think there's a whole lot to be done until we land better support for this is Tup, which mshal mentioned he was working on. We could use this bug or perhaps bug 1499156 to track that work.

Comment 4

[Chris Manchester (limited bugmail, email directly)]

Let's track this with bug 1499156.