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-1060] _SwiftNativeNSError and SwiftObject are defined twice in SwiftRuntimeTests #43672

Open
swift-ci opened this issue Mar 24, 2016 · 5 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. runtime The Swift Runtime

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-1060
Radar None
Original Reporter tbirch (JIRA User)
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Project Infrastructure
Labels Bug, Runtime
Assignee None
Priority Medium

md5: fc0e140de28bd5ac5556f0cf30571c89

Issue Description:

Anything that links against libswiftRuntime.a and libswiftCore.dylib will get two copies of any class defined in libswiftRuntime.a, which is currently _SwiftNativeNSError and SwiftObject.

objc[36230]: Class _SwiftNativeNSError is implemented in both /Users/tbirch/src/build/Ninja-ReleaseAssert/swift-macosx-x86_64/./lib/swift/macosx/libswiftCore.dylib and /Users/tbirch/src/swift/../build//Ninja-ReleaseAssert/swift-macosx-x86_64/unittests/runtime/SwiftRuntimeTests. One of the two will be used. Which one is undefined.
objc[36230]: Class SwiftObject is implemented in both /Users/tbirch/src/build/Ninja-ReleaseAssert/swift-macosx-x86_64/./lib/swift/macosx/libswiftCore.dylib and /Users/tbirch/src/swift/../build//Ninja-ReleaseAssert/swift-macosx-x86_64/unittests/runtime/SwiftRuntimeTests. One of the two will be used. Which one is undefined.
@belkadan
Copy link
Contributor

Why would anything link against both of those, though? Is it just SwiftRuntimeTests?

@swift-ci
Copy link
Collaborator Author

Comment by Tom Birch (JIRA)

Yeah, I think it's just unit testing targets. If objc is built with asserts enabled, it fails an assertion right after printing this error message.

@Dante-Broggi
Copy link
Contributor

Is this resolved, or no longer valid? If either, this should be closed.

@belkadan
Copy link
Contributor

It's still happening.

I don't think these pings are so useful unless you test the issue yourself and see evidence that something has changed.

@Dante-Broggi
Copy link
Contributor

I suppose I might be over doing it, sorry.
I will stop.

However, I was intending to both bring attention to bugs that have been fixed, but also bugs that people have forgotten needed to be fixed.

Also, the week I started doing it (coincidentally or not) was also the first week more bugs were (marked) resolved, than were created that week in the history of bugs.swift.org.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. runtime The Swift Runtime
Projects
None yet
Development

No branches or pull requests

3 participants