STEP 3 FAILED - FIND SYMLINK ISSUE (NOT A MISSING JAR)
The generator make_lab_dex.py failed with:
dex tooling jars missing from ~/.m2
EXACT CAUSE
- The script runs:
find ~/.m2/repository -name '*.jar'
WITHOUT -L.
- /tmp/tools/fakehome/.m2/repository is a symlink to /tmp/tools/m2.
- GNU find does not follow a symlink starting point, so it returns 0 jars.
- The same command with -L returns 92 jars.
Measured:
HOME=/tmp/tools/fakehome bash -c "find ~/.m2/repository -name '*.jar' | wc -l" -> 0
HOME=/tmp/tools/fakehome bash -c "find -L ~/.m2/repository -name '*.jar' | wc -l" -> 92
PROPOSED FIX (NEEDS APPROVAL)
Replace the symlink with a real directory copy (34 MB) so the script's find can walk it:
rm /tmp/tools/fakehome/.m2/repository
mkdir -p /tmp/tools/fakehome/.m2/repository
cp -a /tmp/tools/m2/. /tmp/tools/fakehome/.m2/repository/
Then rerun:
cd /tmp/kilo/clones/doublecloner
HOME=/tmp/tools/fakehome python3 tools/make_lab_dex.py /tmp/tools/lab/src/dcvmlab
VERSION CONFLICT TO FLAG
The m2 repo now contains BOTH:
guava-27.1-android (smali 2.5.2 transitive) AND guava-33.2.1-jre
jcommander-1.64 (smali 2.5.2 transitive) AND jcommander-1.78
The script's classpath includes every guava/jcommander jar it finds, and the first one in
find order wins. REPRODUCE.md wants 33.2.1-jre and 1.78. To force those, delete the older
two from the fake home after the copy.
STATUS
- Step 3: NOT RUN / blocked (generator failed with dex tooling jars missing from ~/.m2)
- Step 4 (NDK build): NOT RUN
- Steps 5-7 (EngineRun, logs, ~/results/): NOT RUN
Approve the real-copy fix and I will rerun Step 3, then continue.