| Git Clone URL: | https://aur.archlinux.org/swift-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | swift-bin |
| Description: | Binary builds of the Swift programming language |
| Upstream URL: | https://www.swift.org/ |
| Keywords: | apple language swift swiftlang |
| Licenses: | Apache |
| Provides: | swift-language |
| Replaces: | swift-language-bin |
| Submitter: | ashleyis |
| Maintainer: | susurri |
| Last Packager: | susurri |
| Votes: | 90 |
| Popularity: | 0.64 |
| First Submitted: | 2015-12-04 17:31 (UTC) |
| Last Updated: | 2025-05-24 03:05 (UTC) |
@frol @SeAL80s: I have a hunch these issues are due to the recent qldv upgrade. I'm likely going to switch to the Fedora RPM binaries once Swift 4.2 comes out, since this whole patching-glibc is a huge mess.
Meanwhile, could you post your glibc version? (pacman -Qi glibc)
Running swift, swiftc and a few other utils I get the following error:
$ swift --help
swift: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: memcpy, version GCC_3.0
Others, e.g. swift-build, swift-run, swift-test, get another error:
$ swift-run
swift-test: relocation error: /usr/lib/libk5crypto.so.3: symbol __ctype_tolower_loc version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference
I am on the latest Arch Linux x64. I recall recent update of GCC to 8.1.0; could that be the trigger? Is there a workaround?
Failed to local test instruction prior to usage of 21680.
ERROR: A failure occurred in package().
Aborting...
What's this ?
Google find nothing !
@tierriminator: Hmm...two questions:
pacman -Qi glibc.)After installation I just get segfaults when trying to run any provided utility
You might get linker warnings when trying to run swift or swift-built binaries after upgrading to glibc 2.27. My patch for the qldv tool (used in PKGBUILD): https://github.com/kirbyfan64/qldv/pull/1
maximaman: Sorry about that! It should be fixed now. (I didn't use the patch, though, because I didn't realize it had been attached...)
Here's a patch which fixes the build of the latest version:
diff --git a/PKGBUILD b/PKGBUILD
index 347027a..0a47d7e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,9 +1,8 @@
# Maintainer: Ryan Gonzalez <rymg19 at gmail dot com>
# Contributor: Frederic Bezies <fredbezies at gmail dot com>, youngunix <>
-_version=4.1
pkgname=swift-bin
-pkgver=${_version//-/.}
+pkgver=4.1
pkgrel=2
pkgdesc="Official binary builds of the Swift programming language."
arch=('x86_64')
@@ -17,8 +16,8 @@ validpgpkeys=('5E4DF843FB065D7F7E24FBA2EF5430F071E1B235')
provides=('swift-language' 'lldb')
replaces=('swift-language-bin')
source=(
-"https://swift.org/builds/swift-${_version}-release/ubuntu1604/swift-${_version}-RELEASE/swift-${_version}-RELEASE-ubuntu16.04.tar.gz"
-"https://swift.org/builds/swift-${_version}-release/ubuntu1604/swift-${_version}-RELEASE/swift-${_version}-RELEASE-ubuntu16.04.tar.gz.sig"
+"https://swift.org/builds/swift-${pkgver}-release/ubuntu1604/swift-${pkgver}-RELEASE/swift-${pkgver}-RELEASE-ubuntu16.04.tar.gz"
+"https://swift.org/builds/swift-${pkgver}-release/ubuntu1604/swift-${pkgver}-RELEASE/swift-${pkgver}-RELEASE-ubuntu16.04.tar.gz.sig"
)
sha256sums=('bd11d422d466dc8fc149e52c4a4a94aa56dc5f03520f482fba5cd7e58f15bbc4'
'SKIP')
@@ -28,7 +27,7 @@ package() {
mkdir -p "${target}"
# Copy extracted files
- cp -Ppr "${srcdir}/swift-${_version}-RELEASE"*/usr/* "$target"
+ cp -Ppr "${srcdir}/swift-${pkgver}-RELEASE"*/usr/* "$target"
rm -rf "${target}/local"
# Permission fix
@@ -40,7 +39,7 @@ package() {
ln -s ../lib/swift/bin/"`basename "$file"`" "${pkgdir}/usr/bin"
done
ln -s swift/lib/libsourcekitdInProc.so "${pkgdir}/usr/lib"
- chmod +x swift/lib/libsourcekitdInProc.so
+ chmod +x ${target}/lib/libsourcekitdInProc.so
# Yuck! patching libedit and libcurl SONAMEs
find "${target}/bin" -type f -exec sed -i 's/libedit\.so\.2/libedit\.so\.0/g' {} \;
I can't build the latest version. It fails with
chmod: cannot access 'swift/lib/libsourcekitdInProc.so': No such file or directory
Swift 4.1 was just released, so before everyone starts asking, this package will be updated either later today or tomorrow.
Pinned Comments