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-834] Very unhelpful error message when clang++ cannot be invoked #5392

Closed
swift-ci opened this issue Feb 27, 2016 · 5 comments
Closed

[SR-834] Very unhelpful error message when clang++ cannot be invoked #5392

swift-ci opened this issue Feb 27, 2016 · 5 comments
Assignees

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-834
Radar rdar://problem/28039322
Original Reporter philipgarnero (JIRA User)
Type Bug
Status Resolved
Resolution Duplicate
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug, Linux
Assignee @abertelrud
Priority Medium

md5: 711f49fece37277d9827e4e8154a0f1e

duplicates:

  • SR-2271 Superconfusing error message when no clang is installed

relates to:

  • SR-6082 Produce a better error message if Swift is run on a system without clang++

Issue Description:

On linux, with version Swift-Ubuntu-14.04-Snapshot-2016-02-25.

I tried to build a small hello world program with a library linked to it and lost a lot of time because the swift build command is pretty silent.
It tells you to use -v to output more but it just shows you what it is doing.
In the end I had to copy all the failing children commands with -v until seeing the real error when clang finally appeared.
And what an error : clang++: command not found.
This is a pretty dumb error but some more complicated errors might give a hard time to the user trying to debug.

It would be great to bring the errors all the way up with or without -v.

@mxcl
Copy link
Contributor

mxcl commented Mar 16, 2016

I don't understand the bug specifically, we don't hide any errors deliberately.

Sounds like something higher in the toolchain is not correctly erroring out.

@abertelrud
Copy link
Contributor

This doesn't sound like an error that came from the tool that was invoked, but rather an error emitted by SwiftPM itself.

@abertelrud
Copy link
Contributor

This is related to SR-2271

@abertelrud
Copy link
Contributor

It's possible that they are in fact the same issue, but there might be a difference between the "no toolchain" case and the "clang failed to be invoked" error

@abertelrud
Copy link
Contributor

After a bunch of testing of what happens when `clang\\` isn't available, I do think that this is the same issue as https://bugs.swift.org/browse/SR-2271. When `clang\\` is available but fails, I get proper error output, so that case seems to have been fixed. I have tried Ubuntu 14.04 and 15.10.

@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
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants