Does not build on Arch Linux #43
Comments
|
There is an issue in the current Package.swift files of the SwiftGtk project and it’s dependencies. It is explained in “ Building the project using swift build” section of #34. It’s only guess but there might be an issue related to SPM. The And/Or you can try following: I have already implemented the pitch in my forks, so you can try, whether the changes I made to the build process solve the issue for you. I have created a demo project for purposes of the PRs I have opened, you can find it here: https://github.com/mikolasstuchlik/Matika. |
|
Here is the result of I'm currently trying to build your fork; I'll let you know the results when it's done. |
|
I attempted to build your fork and unfortunately it did not work. :( |
|
This looks like an issue with the Swift Package Manager to me, rather than an issue with the SwiftGtk itself (=> it might be an issue for the Swift Forum). If there is an issue with the SPM, there is probably nothing I can do for you :( If the problem is unrelated to the SwiftGtk, I think that attempt to compile only .systemLibrary module importing "gio-unix-2.0" should fail aswell. I have created such project when resolving an issue with LLDB. You can find it here https://github.com/mikolasstuchlik/LldbMinimalTest It is quite a simple Swift package, it does nothing. There are three modules, CGLib which uses pkg-config to import "gio-unix-2.0", GLib which adds some settings important for the debugger and LldbMinimalTest which is an executable module. Edit: I get the "non-whitelisted" warning too. mikolas@MIKI-U-NTBK:~/FI-Developer/apps/LldbMinimalTest$ swift package clean
mikolas@MIKI-U-NTBK:~/FI-Developer/apps/LldbMinimalTest$ swift build
'CGLib' gio-unix-2.0.pc: warning: non whitelisted flag(s): -pthread
[7/7] Linking LldbMinimalTest
mikolas@MIKI-U-NTBK:~/FI-Developer/apps/LldbMinimalTest$ |
|
I can build LldbMinimalTest successfully. Strange. Does this mean it's not a problem with the Swift package manager? |
|
Well, I would say that there is an issue with SPM, since build should not ever end by SIGSEGV. The question what triggers the issue (and whether there is a workaround) remains. Would you tell me what version of Arch and Swift toolchain are you using, please? I might have some time to look at the issue myself in following days. |
|
|
Build the latest SPM from https://github.com/apple/swift-package-manager and use it to build. This is a bug in SPM that I fixed in |
|
Okay so i built the latest SPM from the github repo provided and I got the following error when building with the new SPM: |
|
Did you install SPM in the folder of your swift toolchain ? And can you try to build an example project using |
|
I made an example project with |
|
@Dadoum (@jenra-uwu) Hello. First of all - I am not a "linux power user", so excuse my lack of linux proficiency. I have tried to look into the issue myself and I will probably need some guidance. I will desribe all steps I took. [I'm using VBox 6.1 from Ubuntu 20.04] I have:
Then I tried to build and "install" swiftPM where my lack of knowledge hit me so I was unable to "install SPM in the folder of my swift toolchain". I have made following steps:
Then I have started to think about the issue. My lack of understanding "how to install the SPM" lead me to consider, whether I have in fact replaced the SPM since build products also contain libSwiftPM.so and other libraries. I have found no such libraries in the toolchain, also the size of swift-build is around 60M so it migh contain more than just one line of code (as written in the target). I have also searched Github for any PR opened by you on SPM (swiftlang/swift-package-manager#3080). I have checked again and there is no package with more than one package in pkgConfig since the version 12 (of the gir2swift) was released. Since you mentioned in the PR, that the PR resolves the https://bugs.swift.org/browse/SR-13424, I think that the issue is on my side due to being unable to "install the SPM" correcly. Would you please help me to do so? :) Edit2: I need to go now, but I figured out it might be useful to post a stack trace (i needed to rebuild spm with searialize debugging option enabled). I'll look in to this soon but for now I need to go afk. I'll be in touch. |
|
The manual way is to get CentOS toolchain from trunk development on swift.org here and to patch it to replace every needed libraries with this command (to run in extracted toolchain folder):
use this PKGBUILD: # Maintainer: Ryan Gonzalez <rymg19 at gmail dot com>
# Contributor: Frederic Bezies <fredbezies at gmail dot com>, youngunix <>
pkgname=swift-bin
pkgver=5.3.1
pkgrel=1
pkgdesc="Binary builds of the Swift programming language"
arch=('x86_64')
url="https://swift.org"
license=('apache')
depends=('libutil-linux' 'libxml2' 'python2')
makedepends=('patchelf' 'rpmextract')
options=('!strip')
provides=('swift-language')
replaces=('swift-language-bin')
source=("https://swift.org/builds/development/centos8/swift-DEVELOPMENT-SNAPSHOT-2021-01-15-a/swift-DEVELOPMENT-SNAPSHOT-2021-01-15-a-centos8.tar.gz")
sha256sums=('SKIP')
package() {
find_elf_only() {
find "${pkgdir}/usr/lib/swift" \
-executable -type f \
'(' -path '*/bin/*' -o -name '*.so*' ')' \
-not -name '*.py' \
"$@"
}
mkdir -p "${pkgdir}/usr/lib/swift"
cp -Ppr "${srcdir}/swift-DEVELOPMENT-SNAPSHOT-2021-01-15-a-centos8"/usr/* "${pkgdir}/usr/lib/swift"
# Symlink the desired binaries to /usr/bin
mkdir -p "${pkgdir}/usr/bin"
for bin in sourcekit-lsp swift swiftc; do
ln -s "/usr/lib/swift/bin/$bin" "${pkgdir}/usr/bin/$bin"
done
# Patch the binaries to use the changed ncurses names
patchelf=(patchelf)
for lib in ncurses panel form; do
patchelf+=(--replace-needed "lib${lib}.so.6" "lib${lib}w.so")
done
find_elf_only -exec "${patchelf[@]}" {} \;
install -dm755 "${pkgdir}/etc/ld.so.conf.d"
echo '/usr/lib/swift/lib/swift/linux' >> "${pkgdir}/etc/ld.so.conf.d/swift.conf"
}PS: With "yay" AUR helper, the PKGBUILD is located in |
|
I was able to successfully install this version of Swift, but the build process still terminates with a |
|
@Dadoum Thanks for your reply. I will describe all steps in the list below: I have:
[m@mm SwiftHelloGtk]$ swift --version
Swift version 5.4-dev (LLVM a9b8270702a974a, Swift d121d7d55fbcce8)
Target: x86_64-unknown-linux-gnu
[m@mm SwiftHelloGtk]$ swift package --version
Swift Package Manager - Swift 5.4.0-dev
[m@mm SwiftHelloGtk]$ swift build
'CGLib' gio-unix-2.0.pc: warning: prohibited flag(s): -pthread
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) ### Localized description -> just a decorated SIGSEGV message |
|
@Dadoum I have found out something that may be interesting. At the previously mentioned package (https://github.com/mikolasstuchlik/LldbMinimalTest), the build succeeds when I use I came up with that idea by observing the stack trace I posted previously, there is sequence of 4 calls repeating resulting in ~ 8000 calls which is odd. -> See frame frame #4: 0x0000555556314e8c swift-build-new`PCFileFinder.locatePCFile(name="libpng", customSearchPaths=0 values, fileSystem=0x000055555732bed0, self=TSCUtility.PCFileFinder @ 0x00007fffff800ff8) at PkgConfig.swift:95:27
frame #5: 0x000055555631570e swift-build-new`PkgConfig.init(name="libpng", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:151:45
frame #6: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=3 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #7: 0x0000555556315b47 swift-build-new`PkgConfig.init(name="freetype2", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:183:42
frame #8: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=3 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #9: 0x0000555556315b47 swift-build-new`PkgConfig.init(name="harfbuzz", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:183:42
frame #10: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=3 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #11: 0x0000555556315b47 swift-build-new`PkgConfig.init(name="freetype2", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:183:42
frame #12: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=3 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
##....
frame #8775: 0x0000555556315b47 swift-build-new`PkgConfig.init(name="freetype2", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:183:42
frame #8776: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=3 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #8777: 0x0000555556315b47 swift-build-new`PkgConfig.init(name="harfbuzz", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:183:42
frame #8778: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=2 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #8779: 0x0000555556315a6c swift-build-new`PkgConfig.init(name="pango", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:182:35
frame #8780: 0x000055555631806c swift-build-new`getFlags #1 (dependencies=2 values, additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) in PkgConfig.init(name:additionalSearchPaths:diagnostics:fileSystem:brewPrefix:) at PkgConfig.swift:167:31
frame #8781: 0x0000555556315a6c swift-build-new`PkgConfig.init(name="pangocairo", additionalSearchPaths=0 values, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at PkgConfig.swift:182:35
frame #8782: 0x0000555555df6921 swift-build-new`pkgConfigArgs(target=0x00005555573d22d0, diagnostics=0x000055555732ac90, fileSystem=0x000055555732bed0, brewPrefix=nil) at Target+PkgConfig.swift:71:33
frame #8783: 0x0000555555774a16 swift-build-new`BuildPlan.pkgConfig(target=0x00005555573d22d0, self=0x0000555557332800) at BuildPlan.swift:1768:23I suspect there is something wrong in the PkgConfig.swift file but I failed to find such file anywhere on Github. However I think that were getting closer! |
|
On Arch Linux there is a problem between freetype and harfbuzz. They are circular dependent. With normal pkgconf command, it resolve the conflict. On SPM Pkg-config, it does not; the only workaround is to modify the pkg config file (/usr/lib/pkg-config) and to remove from either harfbuzz or freetype the reference to the other |
|
I forgot that I modified that file while ago |
|
Great! I think that this might resolve the issue for you @jenra-uwu :)
As for the issue with circular dependencies. It is my opinion, that SPM should not SIGSEGV under any condition. I think that we should probably report this behavior as a bug. Either teach the SPM how to build such "corrupted" dependencies, assert the issue or report it and end gracefully. I don't have enough time to learn SPM in order to solve the issue myself. Should I create bug report or will you (@Dadoum ) handle this :) ? |
|
Create the bug issue I will try to fix this on my fork (and then try to PR) |
|
OK! :) |
|
|
|
Also don't forget to |
|
@Dadoum After reviewing https://bugs.swift.org/browse/SR-13424, I think that the issue is the same as described in this ticket. I will add our finsing into this ticket (and I won't create a new one) :) I have edited the ticket. |
|
Try to install https://github.com/Dadoum/swift-tools-support-core (you will need to clone swift-package-manager from Apple, change the url in Package.swift, and copy everything from |
|
@Dadoum Is it correct - It won't replace any existing file in |
|
You need to build swift-package-manager with my fork |
|
the only files required are the one that are going to be replaced |
|
OK. I suspect you have modified Package.swift for SPM (package swift-package-manager) already. If so, could you share it with me, please? Edit: nwm - I have just replaced the swift-tools-support-core in the swift-package-manager .build/checkout directory. Edit 2: When I installed the Manjaro today, I created non-resizable 15GB VM drive... well... now I struggle with lack of space 🤦 ... I hate myself 🤣 |
// swift-tools-version:5.1
/*
This source file is part of the Swift.org open source project
Copyright (c) 2014 - 2020 Apple Inc. and the Swift project authors
Licensed under Apache License v2.0 with Runtime Library Exception
See http://swift.org/LICENSE.txt for license information
See http://swift.org/CONTRIBUTORS.txt for Swift project authors
*/
import PackageDescription
import class Foundation.ProcessInfo
// We default to a 10.10 minimum deployment target for clients of libSwiftPM,
// but allow overriding it when building for a toolchain.
let macOSPlatform: SupportedPlatform
if let deploymentTarget = ProcessInfo.processInfo.environment["SWIFTPM_MACOS_DEPLOYMENT_TARGET"] {
macOSPlatform = .macOS(deploymentTarget)
} else {
macOSPlatform = .macOS(.v10_10)
}
let package = Package(
name: "SwiftPM",
platforms: [macOSPlatform],
products: [
// The `libSwiftPM` set of interfaces to programatically work with Swift
// packages. `libSwiftPM` includes all of the SwiftPM code except the
// command line tools, while `libSwiftPMDataModel` includes only the data model.
//
// NOTE: This API is *unstable* and may change at any time.
.library(
name: "SwiftPM",
type: .dynamic,
targets: [
"SourceControl",
"SPMLLBuild",
"PackageCollections",
"LLBuildManifest",
"PackageModel",
"PackageLoading",
"PackageGraph",
"Build",
"Xcodeproj",
"Workspace"
]
),
.library(
name: "SwiftPM-auto",
targets: [
"SourceControl",
"SPMLLBuild",
"LLBuildManifest",
"PackageCollections",
"PackageModel",
"PackageLoading",
"PackageGraph",
"Build",
"Xcodeproj",
"Workspace"
]
),
.library(
name: "SwiftPMDataModel",
type: .dynamic,
targets: [
"SourceControl",
"PackageCollections",
"PackageModel",
"PackageLoading",
"PackageGraph",
"Xcodeproj",
"Workspace"
]
),
.library(
name: "XCBuildSupport",
targets: ["XCBuildSupport"]
),
.library(
name: "PackageDescription",
type: .dynamic,
targets: ["PackageDescription"]
),
],
targets: [
// The `PackageDescription` targets define the API which is available to
// the `Package.swift` manifest files. We build the latest API version
// here which is used when building and running swiftpm without the
// bootstrap script.
.target(
/** Package Definition API */
name: "PackageDescription",
swiftSettings: [
.define("PACKAGE_DESCRIPTION_4_2"),
]),
// MARK: SwiftPM specific support libraries
.target(
name: "Basics",
dependencies: ["SwiftToolsSupport-auto"]),
.target(
/** The llbuild manifest model */
name: "LLBuildManifest",
dependencies: ["SwiftToolsSupport-auto", "Basics"]),
.target(
/** Source control operations */
name: "SourceControl",
dependencies: ["SwiftToolsSupport-auto", "Basics"]),
.target(
/** Shim for llbuild library */
name: "SPMLLBuild",
dependencies: ["SwiftToolsSupport-auto", "Basics"]),
// MARK: Project Model
.target(
/** Primitive Package model objects */
name: "PackageModel",
dependencies: ["SwiftToolsSupport-auto", "Basics"]),
.target(
/** Package model conventions and loading support */
name: "PackageLoading",
dependencies: ["SwiftToolsSupport-auto", "Basics", "PackageModel"]),
// MARK: Package Dependency Resolution
.target(
/** Data structures and support for complete package graphs */
name: "PackageGraph",
dependencies: ["SwiftToolsSupport-auto", "Basics", "PackageLoading", "PackageModel", "SourceControl"]),
// MARK: Package Collections
.target(
/** Data structures and support for package collections */
name: "PackageCollections",
dependencies: ["SwiftToolsSupport-auto", "Basics", "PackageModel", "SourceControl"]),
// MARK: Package Manager Functionality
.target(
/** Builds Modules and Products */
name: "SPMBuildCore",
dependencies: ["SwiftToolsSupport-auto", "Basics", "PackageGraph"]),
.target(
/** Builds Modules and Products */
name: "Build",
dependencies: ["SwiftToolsSupport-auto", "Basics", "SPMBuildCore", "PackageGraph", "LLBuildManifest", "SwiftDriver", "SPMLLBuild"]),
.target(
/** Support for building using Xcode's build system */
name: "XCBuildSupport",
dependencies: ["SPMBuildCore", "PackageGraph"]),
.target(
/** Generates Xcode projects */
name: "Xcodeproj",
dependencies: ["SwiftToolsSupport-auto", "Basics", "PackageGraph"]),
.target(
/** High level functionality */
name: "Workspace",
dependencies: ["SwiftToolsSupport-auto", "Basics", "SPMBuildCore", "PackageGraph", "PackageModel", "SourceControl", "Xcodeproj"]),
// MARK: Commands
.target(
/** High-level commands */
name: "Commands",
dependencies: ["SwiftToolsSupport-auto", "Basics", "Build", "PackageGraph", "SourceControl", "Xcodeproj", "Workspace", "XCBuildSupport", "ArgumentParser", "PackageCollections"]),
.target(
/** The main executable provided by SwiftPM */
name: "swift-package",
dependencies: ["Commands"]),
.target(
/** Builds packages */
name: "swift-build",
dependencies: ["Commands"]),
.target(
/** Runs package tests */
name: "swift-test",
dependencies: ["Commands"]),
.target(
/** Runs an executable product */
name: "swift-run",
dependencies: ["Commands"]),
.target(
/** Interacts with package collections */
name: "swift-package-collection",
dependencies: ["Commands"]),
.target(
/** Shim tool to find test names on OS X */
name: "swiftpm-xctest-helper",
dependencies: [],
linkerSettings: [
.unsafeFlags(["-Xlinker", "-rpath", "-Xlinker", "@executable_path/../../../lib/swift/macosx"], .when(platforms: [.macOS])),
]),
// MARK: Additional Test Dependencies
.target(
/** SwiftPM test support library */
name: "SPMTestSupport",
dependencies: ["SwiftToolsSupport-auto", "Basics", "TSCTestSupport", "PackageGraph", "PackageLoading", "SourceControl", "Workspace", "Xcodeproj", "XCBuildSupport"]),
// MARK: SwiftPM tests
.testTarget(
name: "BasicsTests",
dependencies: ["Basics", "SPMTestSupport"]),
.testTarget(
name: "BuildTests",
dependencies: ["Build", "SPMTestSupport"]),
.testTarget(
name: "CommandsTests",
dependencies: ["swift-build", "swift-package", "swift-test", "swift-run", "Commands", "Workspace", "SPMTestSupport"]),
.testTarget(
name: "WorkspaceTests",
dependencies: ["Workspace", "SPMTestSupport"]),
.testTarget(
name: "FunctionalTests",
dependencies: ["swift-build", "swift-package", "swift-test", "PackageModel", "SPMTestSupport"]),
.testTarget(
name: "FunctionalPerformanceTests",
dependencies: ["swift-build", "swift-package", "swift-test", "SPMTestSupport"]),
.testTarget(
name: "PackageDescription4Tests",
dependencies: ["PackageDescription"]),
.testTarget(
name: "PackageLoadingTests",
dependencies: ["PackageLoading", "SPMTestSupport"],
exclude: ["Inputs"]),
.testTarget(
name: "PackageLoadingPerformanceTests",
dependencies: ["PackageLoading", "SPMTestSupport"]),
.testTarget(
name: "PackageModelTests",
dependencies: ["PackageModel", "SPMTestSupport"]),
.testTarget(
name: "PackageGraphTests",
dependencies: ["PackageGraph", "SPMTestSupport"]),
.testTarget(
name: "PackageGraphPerformanceTests",
dependencies: ["PackageGraph", "SPMTestSupport"]),
.testTarget(
name: "PackageCollectionsTests",
dependencies: ["SPMTestSupport", "PackageCollections"]),
.testTarget(
name: "SourceControlTests",
dependencies: ["SourceControl", "SPMTestSupport"]),
.testTarget(
name: "XcodeprojTests",
dependencies: ["Xcodeproj", "SPMTestSupport"]),
.testTarget(
name: "XCBuildSupportTests",
dependencies: ["XCBuildSupport", "SPMTestSupport"]),
// Examples (These are built to ensure they stay up to date with the API.)
.target(
name: "package-info",
dependencies: ["PackageModel", "PackageLoading", "PackageGraph", "Workspace"],
path: "Examples/package-info/Sources/package-info"
)
],
swiftLanguageVersions: [.v5]
)
// Add package dependency on llbuild when not bootstrapping.
//
// When bootstrapping SwiftPM, we can't use llbuild as a package dependency it
// will provided by whatever build system (SwiftCI, bootstrap script) is driving
// the build process. So, we only add these dependencies if SwiftPM is being
// built directly using SwiftPM. It is a bit unfortunate that we've add the
// package dependency like this but there is no other good way of expressing
// this right now.
/// When not using local dependencies, the branch to use for llbuild and TSC repositories.
let relatedDependenciesBranch = "main"
if ProcessInfo.processInfo.environment["SWIFTPM_LLBUILD_FWK"] == nil {
if ProcessInfo.processInfo.environment["SWIFTCI_USE_LOCAL_DEPS"] == nil {
package.dependencies += [
.package(url: "https://github.com/apple/swift-llbuild.git", .branch(relatedDependenciesBranch)),
]
} else {
// In Swift CI, use a local path to llbuild to interoperate with tools
// like `update-checkout`, which control the sources externally.
package.dependencies += [
.package(path: "../llbuild"),
]
}
package.targets.first(where: { $0.name == "SPMLLBuild" })!.dependencies += ["llbuildSwift"]
}
if ProcessInfo.processInfo.environment["SWIFTCI_USE_LOCAL_DEPS"] == nil {
package.dependencies += [
.package(url: "https://github.com/Dadoum/swift-tools-support-core.git", .branch(relatedDependenciesBranch)),
// The 'swift-argument-parser' version declared here must match that
// used by 'swift-driver' and 'sourcekit-lsp'. Please coordinate
// dependency version changes here with those projects.
.package(url: "https://github.com/apple/swift-argument-parser.git", .upToNextMinor(from: "0.3.1")),
.package(url: "https://github.com/apple/swift-driver.git", .branch(relatedDependenciesBranch)),
]
} else {
package.dependencies += [
.package(path: "../swift-tools-support-core"),
.package(path: "../swift-argument-parser"),
.package(path: "../swift-driver"),
]
} |
|
It gave me this message 🙂 👍 [m@mm LldbMinimalTest]$ /usr/lib/swift/bin/swift-run-new
warning: circular dependency detected while parsing pangocairo: harfbuzz -> freetype2 -> harfbuzz
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: harfbuzz -> freetype2 -> harfbuzz
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: harfbuzz -> freetype2 -> harfbuzz
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: harfbuzz -> freetype2 -> harfbuzz
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
warning: circular dependency detected while parsing pangocairo: freetype2 -> harfbuzz -> freetype2
'CGLib' pangocairo.pc: warning: prohibited flag(s): -pthread, -pthread, -pthread, -pthread
[7/7] Linking LldbMinimalTest
* Build Completed!
Hello, world!
[m@mm LldbMinimalTest]$ |
|
(Also please check out my post in swiftlang/swift-package-manager#3080 (comment)) :) |
|
|
|
@jenra-uwu just to make sure, are you now able to build the project? :) |
|
I'm having an issue that seems to be the same on an install of Fedora 34, using both 5.3.3 and 5.4.1 builds |
|
Can you upload the logs ? I can surely help about this |
|
Sure. There's a page on fedora's error manager, I'll link it and see what I can do on the logs. |
uname |
|
The problem seems to be always the same, there is to many pkgconfig files to load that lead to a stack overflow. Can surely help by caching result. Will upload fork soon |
|
Please try to recompile swift-packaeg-manager but change swift-tools-support-core url in package.swift by this one: https://github.com/Dadoum/swift-tools-support-core |
|
Based on the above comments regarding a circular dependency between freetype and harfbuzz, I edited harfbuzz to not depend on freetype and the issue no longer occurs, so this is the same issue. I'll test the forked spm variant. |
|
I think even the upstream SPM should fix the issue (even if it is very very unefficient) |
On Arch Linux, trying to run
./build.shyields the following error:I believe I have all required packages installed, but what's puzzling is the address boundary error. 🤔
The text was updated successfully, but these errors were encountered: