Skip to content

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Apr 1, 2016

What's in this pull request?

Resolved bug number: (SR-)


Before merging this pull request to apple/swift repository:

  • Test pull request on Swift continuous integration.

Triggering Swift CI

The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:

Smoke Testing

Platform Comment
All supported platforms @swift-ci Please smoke test
OS X platform @swift-ci Please smoke test OS X platform
Linux platform @swift-ci Please smoke test Linux platform

Validation Testing

Platform Comment
All supported platforms @swift-ci Please test
OS X platform @swift-ci Please test OS X platform
Linux platform @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

This unifies the behaviour for imports across the private libc extras and the
public libc shims.

@@ -0,0 +1,50 @@
//===--- Subprocess.cpp - Subprocess Stubs --------------------------------===//
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to name the file Subprocess.cpp?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I named it .c to avoid the extern "C" block. I don't have a strong opinion on that, and can change it you believe it is better.

@gribozavr
Copy link
Contributor

@swift-ci Please test

@compnerd
Copy link
Member Author

compnerd commented Apr 1, 2016

I don't understand the failure on the OS X target. Shouldn't /usr/include/crt_externs.h always exist on the build hosts? The header is used in TaskQueue.inc as well.

@gribozavr
Copy link
Contributor

@swift-ci Please test

@compnerd
Copy link
Member Author

compnerd commented Apr 2, 2016

Interesting, it seems that not all SDKs provide the header. Ive changed it to a forward declaration instead of the header to permit building against any of the SDKs.

@gribozavr
Copy link
Contributor

@swift-ci Please test and merge

@compnerd
Copy link
Member Author

compnerd commented Apr 3, 2016

Seems like another instance of the packaging issues:

swift-build: error: exit(1): which swiftc

during the package tests.

@gribozavr
Copy link
Contributor

Sorry, it is more than that:

https://ci.swift.org/job/swift-PR-osx/732/console

swift/stdlib/private/SwiftPrivateLibcExtras/Subprocess.c:23:10: error: 'posix_spawn_file_actions_init' is unavailable: not available on tvOS
  return posix_spawn_file_actions_init(file_actions);

@compnerd
Copy link
Member Author

compnerd commented Apr 3, 2016

Oh, sorry, I didn't see that when I looked through the failures. Is this really just a declaration issue? Since it would seem that if the function was truly unavailable, then the link would fail (since they are not declared weak).

@gribozavr
Copy link
Contributor

Yes, it is just a declaration. If we can persuade the compiler to create a reference, everything will link just fine.

@compnerd
Copy link
Member Author

compnerd commented Apr 6, 2016

Sorry about the delay. I believe that this version should work on tvOS as well now.

This unifies the behaviour for imports across the private libc extras and the
public libc shims.
@compnerd
Copy link
Member Author

ping?

@gribozavr
Copy link
Contributor

@swift-ci Please test and merge

@swift-ci swift-ci merged commit 3a59497 into swiftlang:master Apr 14, 2016
@modocache modocache mentioned this pull request Apr 19, 2016
1 task
@compnerd compnerd deleted the unit-test-shims branch July 3, 2016 17:24
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

Successfully merging this pull request may close these issues.

4 participants