xml-coding – Build Information – Swift Package Index

Has it really been five years since Swift Package Index launched? Read our anniversary blog post!

Build Information

Failed to build xml-coding, reference 0.4.1 (b6a2ae), with Swift 6.2 (beta) for Wasm on 19 Jun 2025 01:09:14 UTC.

Build Command

bash -c docker run --pull=always --rm -v "checkouts-4606859-3":/host -w "$PWD" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasi 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 4.64.0
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/adam-fowler/xml-coding.git
Reference: 0.4.1
Initialized empty Git repository in /host/spi-builder-workspace/.git/
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
From https://github.com/adam-fowler/xml-coding
 * tag               0.4.1      -> FETCH_HEAD
HEAD is now at b6a2ae2 Fix decoding of optional attributes (#6)
Cloned https://github.com/adam-fowler/xml-coding.git
Revision (git rev-parse @):
b6a2ae25464959f41cd167047ee47fe5bb681c6c
SUCCESS checkout https://github.com/adam-fowler/xml-coding.git at 0.4.1
========================================
Build
========================================
Selected platform:         wasm
Swift version:             6.2
Building package at path:  $PWD
https://github.com/adam-fowler/xml-coding.git
Running build ...
bash -c docker run --pull=always --rm -v "checkouts-4606859-3":/host -w "$PWD" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasi 2>&1
wasm-6.2-latest: Pulling from finestructure/spi-images
Digest: sha256:44384f43f933eaa0f42803e9ef7c3d8388c5841ccc831a15a5edf63d8c273423
Status: Image is up to date for registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest
Building for debugging...
[0/2] Write sources
[1/2] Write swift-version-24593BA9C3E375BF.txt
[3/8] Compiling XMLCoding XMLEncoder.swift
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
[4/8] Compiling XMLCoding XML.swift
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
error: emit-module command failed with exit code 1 (use -v to see invocation)
[5/8] Compiling XMLCoding CollectionCoders.swift
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
[6/8] Compiling XMLCoding XMLDecoder.swift
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
[7/8] Emitting module XMLCoding
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
[8/8] Compiling XMLCoding CodableProperties.swift
/host/spi-builder-workspace/Sources/XMLCoding/XML.swift:10:17: error: no such module 'Foundation'
  8 | // Implemented to replace the XML Foundation classes. This was initially required as there is no implementation of the Foundation XMLNode classes in iOS. This is also here because the implementation of XMLNode in Linux Swift 4.2 was causing crashes. Whenever an XMLDocument was deleted all the underlying CoreFoundation objects were deleted. This meant if you still had a reference to a XMLElement from that document, while it was still valid the underlying CoreFoundation object had been deleted.
  9 |
 10 | import struct   Foundation.Data
    |                 `- error: no such module 'Foundation'
 11 | import class    Foundation.NSObject
 12 | #if canImport(FoundationXML)
BUILD FAILURE 6.2 wasm