It seems the <a href="https://github.com/ungoogled-software/ungoogled-chromium-macos/a

Missing ARM64 build for 112.0.5615.49,about ungoogled-software/ungoogled-chromium-macos

Comments (2)

implicitfield commented on May 28, 2024

Looks like the arm64 build failed to link with the following error:

ld64.lld: error: undefined symbol: extensions::NativeMessagingHostManifest::IsValidName(std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&)
>>> referenced by thinlto-cache/llvmcache-88CDC1F4A3AEE57B2E9AB5A992FF383B92E3C705:(symbol extensions::NativeMessagingHostListPolicyHandler::CheckListEntry(base::Value const&)+0x68)
>>> referenced by thinlto-cache/llvmcache-32D58516DDDF1AE74B95E8A0156ABB18FA6D1A92:(symbol extensions::(anonymous namespace)::NativeProcessLauncherImpl::Core::DoLaunchOnThreadPool(GURL const&, std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&, base::OnceCallback<void (extensions::NativeProcessLauncher::LaunchResult, base::Process, base::File, base::File)>) (.2a5bf1a3f4b77464d235f87d699578f6)+0x40)

ld64.lld: error: undefined symbol: extensions::NativeMessagingHostManifest::~NativeMessagingHostManifest()
>>> referenced by thinlto-cache/llvmcache-32D58516DDDF1AE74B95E8A0156ABB18FA6D1A92:(symbol extensions::(anonymous namespace)::NativeProcessLauncherImpl::Core::DoLaunchOnThreadPool(GURL const&, std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&, base::OnceCallback<void (extensions::NativeProcessLauncher::LaunchResult, base::Process, base::File, base::File)>) (.2a5bf1a3f4b77464d235f87d699578f6)+0x53c)

ld64.lld: error: undefined symbol: extensions::NativeMessagingHostManifest::Load(base::FilePath const&, std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>*)
>>> referenced by thinlto-cache/llvmcache-32D58516DDDF1AE74B95E8A0156ABB18FA6D1A92:(symbol extensions::(anonymous namespace)::NativeProcessLauncherImpl::Core::DoLaunchOnThreadPool(GURL const&, std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&, base::OnceCallback<void (extensions::NativeProcessLauncher::LaunchResult, base::Process, base::File, base::File)>) (.2a5bf1a3f4b77464d235f87d699578f6)+0x90)
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Not sure why CI didn't bail out there and continued anyway (the last two jobs end with the same error.) Unfortunately I can't debug this further, since I was unable to reproduce the linker error locally, albeit on an arm64 host.

from ungoogled-chromium-macos.