Ok, this turned out to be due to me having a customized Cargo config in ~/.cargo/config that instructs Cargo to link with lld. This somehow propagated into the containerized environment and then broke the build. I'm leaving it up to you folks to decide whether the host config being used in the container should be considered an issue or not.
proton 7.0x1 2022-07
When trying to compile latest head (75231818302bdf746d79ddf76e241363b9e2b5e8) from source, I'm running into the following error:
It looks like this sub-component attempts to link with lld, which isn't actually installed in the Docker container you are shipping. I figured it might be due to
lldbeing present on the host and perhaps the configure script accidentally somehow propagating that into the container, but uninstalling LLVM on the host doesn't change anything. I'm on Arch with all packages at their latest version and compile using the podman container runtime. Command executed was simplymake redist.