Skip to content

Don't pass -Werror to ClangImporter's clang when Swift is used from LLDB #13303

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

Merged
merged 1 commit into from
Dec 11, 2017

Conversation

adrian-prantl
Copy link
Contributor

Don't pass -Werror to ClangImporter's clang when Swift is used from within LLDB.

This works a around search path problems caused by a module existing
in both the build/install directory and the source directory.

rdar://problem/35714074

(cherry picked from commit 97f9e4e)

…ithin LLDB.

This works a around search path problems caused by a module existing
in both the build/install directory and the source directory.

<rdar://problem/35714074>

(cherry picked from commit 97f9e4e)
@adrian-prantl
Copy link
Contributor Author

@swift-ci please nominate:

Explanation: This works a around search path problems caused by a module existing in both the build/install directory and the source directory.
Scope: Avoid -Werror in ClangImporter
Radar: rdar://problem/35714074
Risk: Low.
Testing: Regression test in swift.

@adrian-prantl
Copy link
Contributor Author

@swift-ci test

@swift-ci
Copy link
Contributor

swift-ci commented Dec 6, 2017

Build failed
Swift Test Linux Platform
Git Sha - f23c289

@adrian-prantl
Copy link
Contributor Author

@shahmishal
ninja: error: '/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-swift-4.1-branch/buildbot_linux/swift-linux-x86_64/lib/swift/linux/x86_64/swift_begin.o', needed by '../buildbot_linux/foundation-linux-x86_64/Foundation/libFoundation.so', missing and no known rule to make it

@shahmishal
Copy link
Member

@graydon is looking into this issue, we started seeing it after we re-branched swift-4.1-branch from master

@adrian-prantl
Copy link
Contributor Author

@swift-ci test linux platform

@swift-ci
Copy link
Contributor

swift-ci commented Dec 7, 2017

Build failed
Swift Test Linux Platform
Git Sha - f23c289

@shahmishal
Copy link
Member

@swift-ci
Copy link
Contributor

swift-ci commented Dec 7, 2017

Build failed
Swift Test Linux Platform
Git Sha - f23c289

@shahmishal
Copy link
Member

New issue:

Foundation/NSError.swift:285:16: error: use of unresolved identifier '_swift_getDefaultErrorCode'
        return _swift_getDefaultErrorCode(self)
               ^~~~~~~~~~~~~~~~~~~~~~~~~~
Swift._getDefaultErrorCode:3:13: note: did you mean '_getDefaultErrorCode'?

@shahmishal
Copy link
Member

Also, need to revert swiftlang/swift-corelibs-foundation#1322

@shahmishal
Copy link
Member

@adrian-prantl
Copy link
Contributor Author

@swift-ci merge

@adrian-prantl
Copy link
Contributor Author

Who has the permission to merge this?

@adrian-prantl
Copy link
Contributor Author

@bob-wilson Do you have the permission to merge this?

@jrose-apple
Copy link
Contributor

There is no "swift-ci merge". If you've gotten approval to merge this (from the nomination), you can just click the button.

@adrian-prantl
Copy link
Contributor Author

Apparently not:

You're not authorized to merge this pull request.

The button is dimmed for me.

@adrian-prantl
Copy link
Contributor Author

I also couldn't find the place in the github UI where I could look up who is authorized...

@adrian-prantl
Copy link
Contributor Author

Weird, it also says:

This pull request can be automatically merged by project collaborators Only those with write access to this repository can merge pull requests.

I would have expected to be in that group.

@shahmishal
Copy link
Member

@adrian-prantl swift-4.1-branch is under CCC.

@adrian-prantl
Copy link
Contributor Author

@shahmishal so who has the permission to merge branches under CCC?

@shahmishal
Copy link
Member

@tkremenek should be able to approve this PR.

Info from Swift 4.1 Release Process blog:

https://swift.org/blog/swift-4-1-release-process/

All change going into the swift-4.1-branch (outside changes being merged in automatically from master) must go through pull requests that are accepted by the corresponding release manager.

Release Managers
The overall management of the release will be overseen by the following individuals, who will announce when stricter control of change goes into effect for the Swift 4 release as the release converges:

Ted Kremenek is the overall release manager for Swift 4.1.

Frédéric Riss is the release manager for swift-llvm, swift-clang, and swift-compiler-rt.

Ben Cohen is the release manager for the Swift Standard Library.

Tony Parker is the release manager for swift-corelibs-foundation.

Daniel Steffen is the release manager for swift-corelibs-libdispatch.

Brian Croom is the release manager for swift-corelibs-xctest.

Rick Ballard is the release manager for swift-package-manager.

Daniel Dunbar is the release manager for swift-llbuild.

Please feel free to email swift-dev or Ted Kremenek directly concerning any questions about the release management process.

@adrian-prantl
Copy link
Contributor Author

@tkremenek Could you please merge this?

@shahmishal
Copy link
Member

@swift-ci please nominate

@adrian-prantl
Copy link
Contributor Author

@shahmishal (I'm trying to understand the process better.) This PR is already approved. Why did you nominate it again?

@shahmishal
Copy link
Member

Sorry, I wrote it on the wrong PR.

@tkremenek tkremenek merged commit d42954f into swiftlang:swift-4.1-branch Dec 11, 2017
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.

5 participants