Build error in latest copperheados build instructions

[Rudd-O]

[969/1002] including ./test/vts/proto/Android.mk ...
[970/1002] including ./test/vts/runners/target/gtest/Android.mk ...
[971/1002] including ./test/vts/specification/Android.mk ...
[972/1002] including ./test/vts/testcases/codelab/hello_world/Android.mk ...
[973/1002] including ./test/vts/testcases/codelab/hello_world_staging/Android.mk ...
[974/1002] including ./test/vts/testcases/codelab/target_binary/Android.mk ...
[975/1002] including ./test/vts/testcases/fuzz/hal_light/conventional/Android.mk ...
[976/1002] including ./test/vts/testcases/fuzz/hal_light/conventional_standalone/Android.mk ...
[977/1002] including ./test/vts/testcases/host/camera/conventional/2_1/Android.mk ...
[978/1002] including ./test/vts/testcases/host/camera/conventional/3_4/Android.mk ...
[979/1002] including ./test/vts/testcases/host/camera_its/Android.mk ...
[980/1002] including ./test/vts/testcases/host/light/conventional/Android.mk ...
[981/1002] including ./test/vts/testcases/host/reboot/RebootRootRemountTest/Android.mk ...
[982/1002] including ./test/vts/testcases/host/reboot/RebootTest/Android.mk ...
[983/1002] including ./test/vts/testcases/host/shell/Android.mk ...
[984/1002] including ./test/vts/testcases/host/shell_binary_crash_test/Android.mk ...
[985/1002] including ./test/vts/testcases/library/bionic_unit_tests/Android.mk ...
[986/1002] including ./test/vts/testcases/library/bionic_unit_tests_static/Android.mk ...
[987/1002] including ./test/vts/testcases/system/libc/Android.mk ...
[988/1002] including ./test/vts/testcases/system/qtaguid/Android.mk ...
[989/1002] including ./test/vts/testcases/target/hal_lights/Android.mk ...
[990/1002] including ./test/vts/testcases/target/hal_power/Android.mk ...
[991/1002] including ./test/vts/testcases/vts_selftest/test_framework/base_test/Android.mk ...
[992/1002] including ./test/vts/tools/vts-tradefed/Android.mk ...
[993/1002] including ./test/vts/utils/python/archive/Android.mk ...
[994/1002] including ./test/vts/utils/python/coverage/Android.mk ...
[995/1002] including ./tools/apksig/Android.mk ...
[996/1002] including ./tools/external/fat32lib/Android.mk ...
[997/1002] including ./tools/loganalysis/Android.mk ...
[998/1002] including ./tools/test/connectivity/Android.mk ...
[999/1002] including ./tools/tradefederation/contrib/Android.mk ...
[1000/1002] including ./tools/tradefederation/core/Android.mk ...
[1001/1002] including ./vendor/android-prepare-vendor/marlin/opm1.171019.012/vendor/google_devices/marlin/Android.mk ...
[1002/1002] including ./vendor/google_devices/marlin/Android.mk ...
build/core/base_rules.mk:238: error: vendor/google_devices/marlin: MODULE.TARGET.APPS.atfwd already defined by vendor/google_devices/marlin.
14:52:07 ckati failed with: exit status 1

[thestinger]

It looks like you might have a duplicate directory in vendor/. I'd clear it away and regenerate it.

[thestinger]

It looks like you might have a duplicate directory in vendor/. I'd clear it away and regenerate it.

[thestinger]

Make sure there's nothing in the android-prepare-vendor directory because we haven't figured out how to make the build system ignore that directory so it goes through there looking for Android.mk etc.

[thestinger]

Make sure there's nothing in the android-prepare-vendor directory because we haven't figured out how to make the build system ignore that directory so it goes through there looking for Android.mk etc.

[Rudd-O]

Ugh. OK. This was missing in the instructions or perhaps it's because you're using mv and I'm using rsync?

[Rudd-O]

Ugh. OK. This was missing in the instructions or perhaps it's because you're using mv and I'm using rsync?

[thestinger]

Yes, since mv removes it from there. We want to avoid that potential pitfall but we weren't sure how to deal with it. It seems creating an empty Android.mk in the android-prepare-vendor repository may work, it would be helpful if you could try that and see if it avoids breakage when vendor files are left in the android-prepare-vendor directory.

[thestinger]

Yes, since mv removes it from there. We want to avoid that potential pitfall but we weren't sure how to deal with it. It seems creating an empty Android.mk in the android-prepare-vendor repository may work, it would be helpful if you could try that and see if it avoids breakage when vendor files are left in the android-prepare-vendor directory.