Skip to content

symbol(s) not found for architecture x86_64 #1363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
j-f1 opened this issue Jul 3, 2020 · 4 comments
Closed

symbol(s) not found for architecture x86_64 #1363

j-f1 opened this issue Jul 3, 2020 · 4 comments

Comments

@j-f1
Copy link
Member

j-f1 commented Jul 3, 2020

With the Tokamak demo, a clean .build/wasm32-unknown-wasi directory, and .swift-version specified as wasm-DEVELOPMENT-SNAPSHOT-2020-07-02-a, I get this error:

$ carton dev --product TokamakDemo
Polyfill integrity verified: /Users/jed/.carton/static/dev.js
Inferring basic settings...
- swift executable: /Users/jed/.carton/sdk/wasm-DEVELOPMENT-SNAPSHOT-2020-07-02-a/usr/bin/swift
Swift version 5.3-dev (LLVM c5b1848323200a8, Swift 66efa1272c2973b)
Target: x86_64-apple-darwin19.5.0
Parsing package manifest: /Users/jed/.carton/sdk/wasm-DEVELOPMENT-SNAPSHOT-2020-07-02-a/usr/bin/swift package dump-package
Error: Process failed with non-zero exit status and following error output:
/Users/jed/Documents/github-clones/Forks/Tokamak: error: manifest parse error(s):
Undefined symbols for architecture x86_64:
  "_$s18PackageDescription17SupportedPlatformV12MacOSVersionV6v10_15AEvau", referenced from:
      _main in Package-98b7ab.o
ld: symbol(s) not found for architecture x86_64
<unknown>:0: error: link command failed with exit code 1 (use -v to see invocation)
@MaxDesiatov
Copy link

MaxDesiatov commented Jul 3, 2020

I think this is one is an issue caused by the .build directory left over from some other snapshot being inconsistent with what SwiftPM from the new snapshot expects. Most probably if you remove .build and rebuild you'll get either #1365 or #1362.

@MaxDesiatov
Copy link

I think the issue is resolved in wasm-DEVELOPMENT-SNAPSHOT-2020-07-07-a, feel free to reopen otherwise.

@j-f1
Copy link
Member Author

j-f1 commented Jul 8, 2020

I can’t confirm either way because I haven’t been able to reproduce it for a bit but I couldn’t reproduce it in this version either

@MaxDesiatov
Copy link

Cool, no worries. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants