Skip to content
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

[SR-3737] Unable to link system archives in generated Xcode project #5126

Closed
harlanhaskins opened this issue Jan 25, 2017 · 5 comments
Closed
Labels

Comments

@harlanhaskins
Copy link
Collaborator

Previous ID SR-3737
Radar None
Original Reporter @harlanhaskins
Type Bug
Environment

macOS 10.12.4

Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: 6c2fc5247b76dc9b7ebb3f4c47c5845a

Issue Description:

When trying to compile a fresh clone of LLVMSwift, it fails with the following warning for each archive: ld: warning: ignoring file /usr/local/Cellar/llvm/3.9.1/lib/libLLVMCodeGen.a, file was built for archive which is not the architecture being linked (arm64)

Steps to reproduce:

brew install llvm (or have llvm-config 3.9.x in your PATH)
git clone https://github.com/trill-lang/LLVMSwift.git
swift utils/make-pkgconfig.swift
swift package generate-xcodeproj
Attempt to build the project

@belkadan
Copy link

Um. The error message seems correct to me: it's trying to link a file that was built for the host machine rather than the target machine.

@harlanhaskins
Copy link
Collaborator Author

This is entirely on x86 though – the archives are all x86_64 mach binaries, and Xcode's target is x86_64 macOS.

@belkadan
Copy link

Ah, then maybe I got it backwards. But it's still suspicious. I don't think arm64 would come out of nowhere.

@ankitspd
Copy link
Member

Is this still a problem?

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
@ikesyo
Copy link
Collaborator

ikesyo commented Mar 25, 2024

generate-xcodeproj command doesn't exist anymore. Closing.

@ikesyo ikesyo closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants