No matching compiler on iOS bot when using Xcode 10 |
|||
Issue descriptionStarting from https://chromium-review.googlesource.com/c/chromium/src/+/1290572, Chromium assumes that all the iOS bots are using Xcode 10+. WebRTC has a bot that was still using Xcode 9, so I decided to update it in: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1293010. After that CL, the bot started to fail with a new error: https://ci.chromium.org/p/webrtc/builders/luci.webrtc.try/ios_api_framework/12951 FAILED: obj/api/video/video_frame/video_frame_buffer.o /b/s/w/ir/cache/goma/client/gomacc clang++ -MMD -MF obj/api/video/video_frame/video_frame_buffer.o.d -DV8_DEPRECATION_WARNINGS -DNO_TCMALLOC -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DCR_XCODE_VERSION=1000 -DCR_CLANG_REVISION=\"344066-1\" -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DNS_BLOCK_ASSERTIONS=1 -DWEBRTC_ENABLE_PROTOBUF=1 -DWEBRTC_INCLUDE_INTERNAL_AUDIO_DEVICE -DRTC_DISABLE_VP9 -DHAVE_SCTP -DUSE_BUILTIN_SW_CODECS -DWEBRTC_ARCH_ARM64 -DWEBRTC_HAS_NEON -DWEBRTC_LIBRARY_IMPL -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=1 -DWEBRTC_POSIX -DWEBRTC_MAC -DWEBRTC_IOS -DABSL_ALLOCATOR_NOTHROW=1 -I../.. -Igen -I../../third_party/abseil-cpp -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -fcolor-diagnostics -fmerge-all-constants -no-canonical-prefixes -arch arm64 -Wall -Werror -Wextra -Wimplicit-fallthrough -Wthread-safety -Wunguarded-availability -Wundeclared-selector -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-unused-lambda-capture -Wno-null-pointer-arithmetic -Oz -fno-omit-frame-pointer -gdwarf-2 -isysroot /b/s/w/ir/cache/xcode_ios_10l232m.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.0.sdk -stdlib=libc++ -miphoneos-version-min=9.0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wexit-time-destructors -Wglobal-constructors -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wc++11-narrowing -Wimplicit-fallthrough -Wthread-safety -Winconsistent-missing-override -Wundef -Wno-shorten-64-to-32 -std=c++11 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -Wnon-virtual-dtor -Woverloaded-virtual -c ../../api/video/video_frame_buffer.cc -o obj/api/video/video_frame/video_frame_buffer.o GOMA:clang++ compiling ../../api/video/video_frame_buffer.cc:*ERROR*: compiler_proxy:3.86739427sNo matching compiler(clang++ 4.2.1[Apple LLVM version 10.0.0 (clang-1000.10.43.1)] (5100c9537c391582c519f3d4702f5b1dfac5f28c78fd975e353330527a2c3bb3)) found in server GOMA:clang++ compiling ../../api/video/video_frame_buffer.cc:*ERROR*: compiler_proxy:3.868179487s/usr/bin/clang++ is disabled. [15/2566] CXX obj/api/video/video_frame/video_source_interface.o FAILED: obj/api/video/video_frame/video_source_interface.o
,
Oct 23
Here are the GN arguments: target_os="ios" ios_enable_code_signing=false use_xcode_clang=true is_component_build=false is_debug=false target_cpu="arm64" ios_deployment_target="9.0" rtc_libvpx_build_vp9=false enable_ios_bitcode=false use_goma=true goma_dir="/b/s/w/ir/cache/goma/client" enable_ dsyms=true enable_stripping=true
,
Oct 23
Can I ask you to move 10a254a instead of 10l232m? ref: https://chromium-review.googlesource.com/c/chromium/src/+/1278332 Goma backend seems not have the version of Xcode10.
,
Oct 23
Thanks for the suggestion. I created: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1296515.
,
Oct 23
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/0b6f136b31923b5a1104de61175d937abb1b26b6 commit 0b6f136b31923b5a1104de61175d937abb1b26b6 Author: Mirko Bonadei <mbonadei@chromium.org> Date: Tue Oct 23 19:40:38 2018 Bump Xcode version on ios_api_framework. The compiler configuration is assuming Xcode 10.0+ [1] while this trybot was still using Xcode 9. This is blocking the Chromium roll into WebRTC. [1] - https://chromium-review.googlesource.com/c/chromium/src/+/1290572 Bug: 898086 Change-Id: Ibb79aaafbdef2ad01f66f6deb01d0e709c057f82 Reviewed-on: https://chromium-review.googlesource.com/c/1296515 Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> [modify] https://crrev.com/0b6f136b31923b5a1104de61175d937abb1b26b6/scripts/slave/recipes/webrtc/ios_api_framework.py [modify] https://crrev.com/0b6f136b31923b5a1104de61175d937abb1b26b6/scripts/slave/recipes/webrtc/ios_api_framework.expected/build_ok.json [modify] https://crrev.com/0b6f136b31923b5a1104de61175d937abb1b26b6/scripts/slave/recipes/webrtc/ios_api_framework.expected/build_failure.json [modify] https://crrev.com/0b6f136b31923b5a1104de61175d937abb1b26b6/scripts/slave/recipes/webrtc/ios_api_framework.expected/trybot_build.json
,
Oct 23
It worked. Thanks tikuta@ for your help! |
|||
►
Sign in to add a comment |
|||
Comment 1 by mbonadei@chromium.org
, Oct 23