[SR-60] exit status 127 when compiling a C dependency #818
Comments
|
Yes, swift-build-tool is still missing a lot of diagnostics in cases like this. Can you make a self contained example that demonstrates this issue? If I try the attached example I just get: $ swift build
Cloning Packages/CLibPQ
Compiling Swift Module 'swiftpqexample2' (1 sources)
/Volumes/Data/ddunbar/Downloads/swiftpq-example-2/Packages/CLibPQ-1.0.0/module.modulemap:2:12: error: header '/usr/local/include/libpq-fe.h' not found
header "/usr/local/include/libpq-fe.h"
^
/Volumes/Data/ddunbar/Downloads/swiftpq-example-2/main.swift:1:8: error: could not build Objective-C module 'CLibPQ'
import CLibPQ
^
<unknown>:0: error: build had 1 command failures
swift-build: exit(1): ["/Library/Developer/Toolchains/swift-2.2-SNAPSHOT-2015-12-01-a.xctoolchain/usr/bin/swift-build-tool", "-f", "/Volumes/Data/ddunbar/Downloads/swiftpq-example-2/.build/debug/swiftpq-example-2.o/llbuild.yaml"]and I would rather not try and install system dependencies just to reproduce this bug. |
|
So, I've actually only been able to reproduce this on Ubuntu 14.04 with the dependency explicitly not available. |
|
Can you include the output of $ strace swift-build-tool -v -f /users/u21/harlan/swiftpq-example/.build/debug/CLibPQ.o/llbuild.yaml |
|
I actually don't have sudo access on that box, and strace needs it... |
|
However I can also reproduce it using this package punctual.tar |
|
Similar issue in SR-81 |
|
Has this been resolved? If so, it should be marked as such. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attachment: Download
Additional Detail from JIRA
md5: a9392c86279ac6b5993728f91ac4a1a8
relates to:
Issue Description:
I looked through my system and it turns out the header doesn't resolve. swift-build-tool doesn't seem to have a sophisticated error handling routine for unresolved dependencies.
swift-build: exit(127): ["swift-build-tool", "-v", "-f", "/users/u21/harlan/swiftpq-example/.build/debug/CLibPQ.o/llbuild.yaml"]
The text was updated successfully, but these errors were encountered: