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

Attempt to diagnose #33844 #33979

Merged
merged 1 commit into from
Jun 1, 2016
Merged

Conversation

retep998
Copy link
Member

#33844 is a spurious failure that causes builds to fail due to the linker command sometimes failing with error 206, which means that the command is too long. This PR makes rustc print out the linker arguments in that case so the reason for it being so long can be diagnosed and hopefully fixed.

r? @alexcrichton

@retep998
Copy link
Member Author

Picture evidence that this PR prints out the linker arguments in that failure case.

@@ -40,7 +40,9 @@ pub fn gnu_target(target: &str) -> String {
}

pub fn cc2ar(cc: &Path, target: &str) -> PathBuf {
if target.contains("musl") || target.contains("msvc") {
if target.contains("msvc") {
PathBuf::from("lib")
Copy link
Member

Choose a reason for hiding this comment

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

Can this change be saved for later? Papering over this unfortunately probably won't fix much, the syntax for calling lib is very different than ar, so this will never work if it's actually used. This should basically just return an option and then it's handled elsewhere when it's not available

Copy link
Member Author

Choose a reason for hiding this comment

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

It fixes the sanity check. In all cases where cc2ar is called or the .ar() of the Build is called, the result is never used on msvc, except for the sanity check. But I'll move it to a separate PR and do the Option thing.

Needed to diagnose rust-lang#33844

Signed-off-by: Peter Atashian <retep998@gmail.com>
@retep998 retep998 force-pushed the why-the-long-face branch 2 times, most recently from a1edc05 to d34ad3c Compare May 31, 2016 20:30
@retep998
Copy link
Member Author

Updated to always print out the linker command if rustc fails to invoke the linker.

@alexcrichton
Copy link
Member

@bors: r+ d34ad3c p=1

Thanks! Also upping the priority to see if we can diagnose sooner.

@bors
Copy link
Contributor

bors commented May 31, 2016

⌛ Testing commit d34ad3c with merge 54c0f00...

@bors
Copy link
Contributor

bors commented May 31, 2016

💔 Test failed - auto-linux-64-cross-armhf

@retep998
Copy link
Member Author

Try to diagnose one spurious failure, get bitten by an entirely different spurious failure...

#33778
#33986

@alexcrichton
Copy link
Member

@bors: retry

On Tue, May 31, 2016 at 3:47 PM, Peter Atashian notifications@github.com
wrote:

Try to diagnose one spurious failure, get bitten by an entirely different
spurious failure...

#33778 #33778
#33986 #33986


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#33979 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAD95OnFuKLBIhYUDQ4XjsXsZQdVz8dUks5qHLp8gaJpZM4IqW3u
.

@bors
Copy link
Contributor

bors commented Jun 1, 2016

⌛ Testing commit d34ad3c with merge ad5fbaf...

bors added a commit that referenced this pull request Jun 1, 2016
Attempt to diagnose #33844

#33844 is a spurious failure that causes builds to fail due to the linker command sometimes failing with error 206, which means that the command is too long. This PR makes rustc print out the linker arguments in that case so the reason for it being so long can be diagnosed and hopefully fixed.

r? @alexcrichton
@bors bors merged commit d34ad3c into rust-lang:master Jun 1, 2016
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.

3 participants