Android arm64 Builder compilation fails |
||
Issue descriptionhttps://build.chromium.org/p/chromium.android/builders/Android%20arm64%20Builder%20%28dbg%29/builds/9475 util.build_utils.CalledProcessError: Command failed: ( cd /b/c/b/Android_arm64_Builder__dbg_/src/out/Debug; java -classpath lib.java/rezip_apk.jar RezipApk renamealign gen/chrome/android/chrome_public_apk/chrome_public_apk.apk_intermediates.unfinished.apk /tmp/tmpjXAfPK ) Exception in thread "main" java.lang.UnsupportedOperationException: Found more than one library Multiple libraries are not supported for APKs that use 'load_library_from_zip'. See crbug/388223. Note, check that your build is clean. An unclean build can incorrectly incorporate old libraries in the APK. at RezipApk.rezip(RezipApk.java:323) at RezipApk.main(RezipApk.java:441)
,
Oct 12 2016
Copy of what I posted on the original patch after the revert: It turns out the crazy linker and VR Shell don't play nice since the linker only likes having a single .so (but only on 64 bit apparently? 32 bit and the FYI bot this was enabled on were fine). There's a .a in the works that should fix the issue (as well as reducing the binary size), but it's been delayed a bit. I was aware that a .a was in the works, but thought it only addressed the binary size. Will attempt re-land patch after that is in. .a status at https://buganizer.corp.google.com/issues/31479702
,
Feb 28 2017
I'm (finally) closing this. The .a that's allowed VR compilation with non-component builds has been in for a rather long time, and VR functionality has been on be default for a while, as well. |
||
►
Sign in to add a comment |
||
Comment 1 by tedc...@chromium.org
, Oct 12 2016Status: Assigned (was: Available)