We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Attachment: Download
Observed in Manjaro Linux, 20.0 and 20.1, with the swift-bin AUR package. (CentOS toolchain with library name patches)
md5: d6c64958297b6bc1804042e9d37c4f1f
Issue Description:
On Arch-Linux-based distributions, using a system library with a pkgConfig arg will make SPM segfault. This is due to the use of realpath here
Edit: added lldb debugger trace
The text was updated successfully, but these errors were encountered:
@swift-ci create
Sorry, something went wrong.
Comment by Mikoláš Stuchlík (JIRA)
This issue was discussed by the SwiftGtk developers in rhx/SwiftGtk#43 .
I have built SPM from main using -serialize-debugging-options frontend option and run build command in lldb. The result is in file trace.txt
The issue is caused by circular dependencies in .pc files on Arch which results in looping the PkgConfig initializer.
Example of such behavior can be observed, when attempting to add package `pangocairo` using pkgConfig.
No branches or pull requests
Attachment: Download
Environment
Observed in Manjaro Linux, 20.0 and 20.1, with the swift-bin AUR package. (CentOS toolchain with library name patches)
Additional Detail from JIRA
md5: d6c64958297b6bc1804042e9d37c4f1f
Issue Description:
On Arch-Linux-based distributions, using a system library with a pkgConfig arg will make SPM segfault. This is due to the use of realpath here
Edit: added lldb debugger trace
The text was updated successfully, but these errors were encountered: