Foundation build failing

Hi,

I've downloaded the latest Xcode (beta 5), using the
swift-3.1-DEVELOPMENT-SNAPSHOT-2017-03-19-a
toolchain and also pulled down the latest code from Apple master but when I
run the build in Xcode it fails with the following errors:

Undefined symbols for architecture x86_64:

  "__T015SwiftFoundation014__CFInitializeA0yyF", referenced from:

      ___CFInitialize in libCoreFoundation.a(CFRuntime.o)

  "__T015SwiftFoundation21__CFSwiftGetBaseClasss9AnyObject_pXpyF",
referenced from:

      ___CFInitialize in libCoreFoundation.a(CFRuntime.o)

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see
invocation)

A colleague also sees this problem, can anyone else reproduce it and does
anyone know how to fix it?

Thanks,
David

This is because mangling changed and that was pushed before the toolchain
was updated to the new mangling.

Revert this commit: https://github.com/apple/swift-corelibs-
foundation/commit/60c8b4e0a9cd364f42056a83705985ef0849b374

···

---------- Forwarded message ----------
From: Philippe Hausler <phausler@apple.com>
Date: Thu, Mar 23, 2017 at 1:41 PM
Subject: Re: [swift-corelibs-dev] Foundation build failing
To: David Dunn <ddunnibm@gmail.com>

Sent from my iPhone

On Mar 23, 2017, at 6:24 AM, David Dunn via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote:

Hi,

I've downloaded the latest Xcode (beta 5), using the
swift-3.1-DEVELOPMENT-SNAPSHOT-2017-03-19-a toolchain and also pulled down
the latest code from Apple master but when I run the build in Xcode it
fails with the following errors:

Undefined symbols for architecture x86_64:

  "__T015SwiftFoundation014__CFInitializeA0yyF", referenced from:

      ___CFInitialize in libCoreFoundation.a(CFRuntime.o)

  "__T015SwiftFoundation21__CFSwiftGetBaseClasss9AnyObject_pXpyF",
referenced from:

      ___CFInitialize in libCoreFoundation.a(CFRuntime.o)

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see
invocation)

A colleague also sees this problem, can anyone else reproduce it and does
anyone know how to fix it?

Thanks,
David

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev