You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
Additional Detail from JIRA
md5: 711f49fece37277d9827e4e8154a0f1e
duplicates:
clang
is installedrelates to:
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.
The text was updated successfully, but these errors were encountered: