New issue
Advanced search Search tips

Issue 905480 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 15
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Chromium build for aarch64 is broken

Project Member Reported by cavalcantii@chromium.org, Nov 14

Issue description

Around 1 1/2 week ago the build was working fine for ARM linux 64bits but it is now broken with the following compiler error:

adenilson@chrome-monster:~/chromium/src$ ninja -C out/armlinux/ image_decode_bench content_shell -j64
ninja: Entering directory `out/armlinux/'
[54/19280] SOLINK clang_x64_v8_arm64/swiftshader/libGLESv2.so
FAILED: clang_x64_v8_arm64/swiftshader/libGLESv2.so clang_x64_v8_arm64/swiftshader/libGLESv2.so.TOC 
python "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="nm" --sofile="clang_x64_v8_arm64/swiftshader/libGLESv2.so" --tocfile="clang_x64_v8_arm64/swiftshader/libGLESv2.so.TOC" --output="clang_x64_v8_arm64/swiftshader/libGLESv2.so" -- ../../third_party/llvm-build/Release+Asserts/bin/clang++ -shared -Wl,--version-script=../../third_party/swiftshader/src/OpenGL/libGLESv2/libGLESv2.lds -Wl,--fatal-warnings -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -m64 -Wl,-O2 -Wl,--gc-sections -rdynamic -nostdlib++ --sysroot=../../build/linux/debian_sid_amd64-sysroot -L../../build/linux/debian_sid_amd64-sysroot/usr/local/lib/x86_64-linux-gnu -Wl,-rpath-link=../../build/linux/debian_sid_amd64-sysroot/usr/local/lib/x86_64-linux-gnu -L../../build/linux/debian_sid_amd64-sysroot/lib/x86_64-linux-gnu -Wl,-rpath-link=../../build/linux/debian_sid_amd64-sysroot/lib/x86_64-linux-gnu -L../../build/linux/debian_sid_amd64-sysroot/usr/lib/x86_64-linux-gnu -Wl,-rpath-link=../../build/linux/debian_sid_amd64-sysroot/usr/lib/x86_64-linux-gnu -Werror -Wl,--gc-sections -Wl,--hash-style=both -o "clang_x64_v8_arm64/swiftshader/libGLESv2.so" -Wl,-soname="libGLESv2.so" @"clang_x64_v8_arm64/swiftshader/libGLESv2.so.rsp"
ld.lld: error: undefined symbol: LLVMInitializeX86TargetInfo
>>> referenced by LLVMReactor.cpp
>>>               clang_x64_v8_arm64/obj/third_party/swiftshader/src/Reactor/swiftshader_reactor/LLVMReactor.o:(rr::Nucleus::Nucleus())

ld.lld: error: undefined symbol: LLVMInitializeX86Target
>>> referenced by LLVMReactor.cpp
>>>               clang_x64_v8_arm64/obj/third_party/swiftshader/src/Reactor/swiftshader_reactor/LLVMReactor.o:(rr::Nucleus::Nucleus())

ld.lld: error: undefined symbol: LLVMInitializeX86TargetMC
>>> referenced by LLVMReactor.cpp
>>>               clang_x64_v8_arm64/obj/third_party/swiftshader/src/Reactor/swiftshader_reactor/LLVMReactor.o:(rr::Nucleus::Nucleus())

ld.lld: error: undefined symbol: LLVMInitializeX86AsmPrinter
>>> referenced by LLVMReactor.cpp
>>>               clang_x64_v8_arm64/obj/third_party/swiftshader/src/Reactor/swiftshader_reactor/LLVMReactor.o:(rr::Nucleus::Nucleus())

ld.lld: error: undefined symbol: LLVMInitializeX86AsmParser
>>> referenced by LLVMReactor.cpp
>>>               clang_x64_v8_arm64/obj/third_party/swiftshader/src/Reactor/swiftshader_reactor/LLVMReactor.o:(rr::Nucleus::Nucleus())
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[117/19280] CXX clang_x64_v8_arm64/obj/third_party/webrtc/rtc_base/rtc_base/physicalsocketserver.o



The configuration used was:
# Build arguments go here.
# See "gn args <out_dir> --list" for available build arguments.
target_os = "linux"
target_cpu = "arm64"  # (default)
is_debug = false  # (default)

# Other args you may want to set:
#is_component_build = true
is_clang = true
symbol_level = 0


 
Cc: sugoi@chromium.org capn@chromium.org
Labels: OS-Linux
Status: Available (was: Untriaged)
Adding owners of related dependency (swiftshader).

It seems the last good hash was: 2f490f064772811703a0f8a7b2ec38805841f2c3

That was just before this patch (which seems to change architecture llvm backends): https://swiftshader-review.googlesource.com/c/22208


Labels: -Pri-3 Pri-1
Cc: cavalcantii@chromium.org
Owner: capn@chromium.org
Status: Started (was: Available)
Fixed by https://swiftshader-review.googlesource.com/22408. Just needs a DEPS roll of SwiftShader.

What's the justification for making this Pri-1 ? Is there any build bot that's broken (I'm only seeing two Fuchsia ARM64 bots, and they're green)? What can we do to prevent this from reoccurring?
The roll has just landed.

cavalcantii@, can you tell us if you failures disappear with the new roll?
Status: Verified (was: Started)
@capn: I guess is safe to say that Fuchsia != Linux@aarch64. It would be nice to have a bot for the later case, to avoid such scenario.

@sugoi: It is building fine now, thanks.

Sign in to add a comment