Arch Linux User Repository

Many thanks for the feedback. But there are so many packages depending on python-sphinx that it is difficult for me to remove it. Maybe we should post an issue somewhere else if this is not directly related to Arch. In your opinion where is the problem lying ? In the swift build, in python-sphinx incompatibility or in the Arch packages incompatibility ?

@Tabsc sphinx version 2.X+ is actually the python-sphinx version (the python 3 version). So if you want this to work, you need to remove python-sphinx. Yes it is confusing that sphinx 2.X+ is for python 3 and version sphinx <2.X ie version 1.X is for python 2.

Comfirm @joekiller error occurs for me as well.

I was not able to remove python2-sphinx since it is installed as a dependency of the package (it thus reinstall itself at each pkgbuild). I tried to put python 3 sphinx as a dep in the PKGBUILD instead of python2-sphinx but it did not work.

So I kept getting

Warning, treated as error:
/home/jlawson/.cache/yay/swift-language/src/swift/docs/ARCOptimization.rst:100:Pygments lexer name 'sil' is not known
[907/950] Compiling /home/jlawson/.cache/yay/swift-...inux-x86_64/stdlib/public/core/linux/x86_64/Swift.o
ninja: build stopped: subcommand failed.
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
==> ERROR: A failure occurred in build().
    Aborting...

Again and finally traced it down to having both python-sphinx and python2-sphinx installed. Once I got rid of sphinx 2+ it went fine.

I had to move into my cache directory (~/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64) and run ninja -d explain to see what the heck was going on. Frustrating but finally it is working again.

It looks like lldb hasn't been updated to work with swig 4 yet, so I created a swig3 AUR package which can be installed side-by-side with swig, and updated swift to use it for now until a better fix can be made.

I've also re-enabled the sourcekit (libsourcekitdInProc.so) build.

I ran strace on the command that fails. Python can't find swig_runtime_data4. It tries various suffixes on it of .so, module.so, .py, .pyc in the library path. Has anyone reported this (or found an existing report for this) at bugs.swift.org? I can't find one, myself.

I confirm.

@imkerberos can confirm getting same error, looks like the system installed swig 4 package conflicted with the version provided by the swift bois

AIL: Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift (2736 of 4876)
******************** TEST 'Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift' FAILED ********************
Script:
--
: 'RUN: at line 1';   rm -rf "/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64/Runtime/Output/linux-fatal-backtrace.swift.tmp" && mkdir -p "/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64/Runtime/Output/linux-fatal-backtrace.swift.tmp"
: 'RUN: at line 2';   /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/bin/swiftc -target x86_64-unknown-linux-gnu  -module-cache-path '/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/swift-test-results/x86_64-unknown-linux-gnu/clang-module-cache' -swift-version 4   /home/kerberos/.cache/yay/swift-language/src/swift/test/Runtime/linux-fatal-backtrace.swift -o /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out
: 'RUN: at line 3';   not --crash /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out 2>&1 | PYTHONPATH=/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/lldb-linux-x86_64/lib/python2.7/site-packages /home/kerberos/.cache/yay/swift-language/src/swift/utils/symbolicate-linux-fatal /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64/Runtime/Output/linux-fatal-backtrace.swift.tmp/a.out - | /home/kerberos/.cache/yay/swift-language/src/swift/utils/backtrace-check -u
--
Exit Code: 1

Command Output (stderr):
--
Traceback (most recent call last):
  File "/home/kerberos/.cache/yay/swift-language/src/swift/utils/symbolicate-linux-fatal", line 32, in <module>
    import lldb
  File "/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/lldb-linux-x86_64/lib/python2.7/site-packages/lldb/__init__.py", line 1499, in <module>
    class SBAddress(object):
  File "/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/lldb-linux-x86_64/lib/python2.7/site-packages/lldb/__init__.py", line 1665, in SBAddress
    __swig_getmethods__["module"] = GetModule
NameError: name '__swig_getmethods__' is not defined
Traceback (most recent call last):
  File "/home/kerberos/.cache/yay/swift-language/src/swift/utils/backtrace-check", line 84, in <module>
    main()
  File "/home/kerberos/.cache/yay/swift-language/src/swift/utils/backtrace-check", line 80, in main
    assert(found_stack_trace_entry)
AssertionError

--

********************
Testing Time: 645.13s
********************
Failing Tests (1):
    Swift(linux-x86_64) :: Runtime/linux-fatal-backtrace.swift

  Expected Passes    : 3613
  Expected Failures  : 43
  Unsupported Tests  : 1219
  Unexpected Failures: 1

4 warning(s) in tests.
FAILED: test/CMakeFiles/check-swift-linux-x86_64 
cd /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test && /usr/bin/cmake -E remove_directory /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/./swift-test-results/x86_64-unknown-linux-gnu && /usr/bin/cmake -E make_directory /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/./swift-test-results/x86_64-unknown-linux-gnu && /usr/bin/python2.7 /home/kerberos/.cache/yay/swift-language/src/llvm/utils/lit/lit.py --incremental -sv --xunit-xml-output=/home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/./swift-test-results/x86_64-unknown-linux-gnu/lit-tests.xml --param swift_test_subset=primary --param swift_test_mode=optimize_none /home/kerberos/.cache/yay/swift-language/src/build/Ninja-ReleaseAssert/swift-linux-x86_64/test-linux-x86_64
ninja: build stopped: subcommand failed.
./utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
==> ERROR: A failure occurred in check().
    Aborting...
Error making: swift-language (swift swift-lldb)

I tested with version 5.0.1 and can confirm sourcekit (libsourcekitdInProc.so) now builds successfully.