Building on Arch Linux with GGC 5.3 & binutils 2.26 halts on "error: unsupported reloc 42" #193

Closed
Siosm opened this Issue Feb 29, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@Siosm

Siosm commented Feb 29, 2016

Building on Arch Linux with GGC 5.3 & binutils 2.26 halts on "error: unsupported reloc 42". Downgrading to GCC 5.2 and binutils 2.25 "fixes" the issue. Thus this is most probably an upstream issue.

Sample from the build output:

out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_resolution_trampoline: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_resolution_trampoline: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_generic_jni_trampoline: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_to_interpreter_bridge: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_to_interpreter_bridge: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_instrumentation_entry: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_instrumentation_exit: error: unsupported reloc 42
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_deoptimize: error: unsupported reloc 42

The "fix" reported at https://groups.google.com/forum/#!topic/android-x86/xtmwv4Dw8l0 does not work and turns the error into "unsupported reloc 43".

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 29, 2016

Contributor

It's not an issue we can act on. Just disable Clang there if needed by your build environment. Alternatively, build in a an Ubuntu LTS container which is what Android supports.

Contributor

thestinger commented Feb 29, 2016

It's not an issue we can act on. Just disable Clang there if needed by your build environment. Alternatively, build in a an Ubuntu LTS container which is what Android supports.

@thestinger thestinger closed this Feb 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment