On a recent test build there were compile errors with libdispatch, even after a clean build:
src/libdispatch.so: error: undefined reference to '__atomic_fetch_sub_4'
src/libdispatch.so: error: undefined reference to '__atomic_load_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_add_4'
src/libdispatch.so: error: undefined reference to '__atomic_compare_exchange_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_or_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_and_4'
src/libdispatch.so: error: undefined reference to '__atomic_store_4'
src/libdispatch.so: error: undefined reference to '__atomic_exchange_4'
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
https://ci.swift.org/job/swift-corelibs-foundation-PR-Linux/245/consoleFull#-12390007823122a513-f36a-4c87-8ed7-cbc36a1ec144
https://github.com/apple/swift-corelibs-foundation/pull/1189
The changes aren't to do with libdispatch and shouldn't have caused these issues (they were related to test code only).
Could this be due to recent build toolchain updates on the build servers?
Alex
These problems have since been fixed, and foundation builds are going through as expected.
Alex
ยทยทยท
On 11 Oct 2017, at 22:03, Alex Blewitt via swift-dev <swift-dev@swift.org> wrote:
On a recent test build there were compile errors with libdispatch, even after a clean build:
src/libdispatch.so: error: undefined reference to '__atomic_fetch_sub_4'
src/libdispatch.so: error: undefined reference to '__atomic_load_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_add_4'
src/libdispatch.so: error: undefined reference to '__atomic_compare_exchange_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_or_4'
src/libdispatch.so: error: undefined reference to '__atomic_fetch_and_4'
src/libdispatch.so: error: undefined reference to '__atomic_store_4'
src/libdispatch.so: error: undefined reference to '__atomic_exchange_4'
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)