You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
libicudataswift.so.65 missing using --configuration debug #4
I'm trying to adopt swift-lambda to replace Fabian's process, but my lambda gets a runtime error:
START RequestId: b4ca0e88-b5f5-44c3-99ed-7ab83cf010b3 Version: $LATEST
/var/task/bootstrap: error while loading shared libraries: libicudataswift.so.65: cannot open shared object file: No such file or directory
END RequestId: b4ca0e88-b5f5-44c3-99ed-7ab83cf010b3
REPORT RequestId: b4ca0e88-b5f5-44c3-99ed-7ab83cf010b3 Duration: 80.48 ms Billed Duration: 100 ms Memory Size: 128 MB Max Memory Used: 6 MB
RequestId: b4ca0e88-b5f5-44c3-99ed-7ab83cf010b3 Error: Runtime exited with error: exit status 127
Runtime.ExitError
I'm afraid I won't have the opportunity to look more into this now, although I hope to be able to do so next week. But I'd appreciate any suggestions in the meantime... perhaps I'm missing something really obvious?
Just realised that I never tried deploying a lambda built with --configuration release - and the output of swift lambda build seems to be quite different with --configuration debug:
$ swift lambda build \
--verbose \
--configuration debug \
--product hiya-apps-call-log-endpoint
Build setup:
Checkout dir: /Users/alfavata/Code/ios-hiya/CallLogLambda/.build/checkouts
Build status:
Package resolved: no
resolved:
package: /Users/alfavata/Code/ios-hiya/CallLogLambda/Package.swift
SDK: /usr/local/lib/swift/dst/x86_64-unknown-linux/swift-5.3-amazonlinux2.xtoolchain/x86_64-amazonlinux2.sdk
SPM: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift build --configuration debug --destination /usr/local/lib/swift/dst/x86_64-unknown-linux/swift-5.3-amazonlinux2.xtoolchain/destination.json -Xswiftc -target -Xswiftc x86_64-unknown-linux -Xcc -target -Xcc x86_64-unknown-linux -Xcc -Wno-unused-command-line-argument --product hiya-apps-call-log-endpoint
[14/14] Linking hiya-apps-call-log-endpoint
Preparing build directory: /Users/alfavata/Code/ios-hiya/CallLogLambda/.build/lambda
Embedding: libswiftSwiftOnoneSupport.so
Not embedding: libpthread.so.0
Not embedding: libdl.so.2
Embedding: libswiftCore.so
Not embedding: libstdc++.so.6
Not embedding: libm.so.6
Not embedding: libgcc_s.so.1
Not embedding: libc.so.6
Already embedded: libswiftCore.so
Embedding: libFoundation.so
Embedding: libswiftDispatch.so
Embedding: libicuucswift.so.65
Embedding: libicui18nswift.so.65
Embedding: libdispatch.so
Embedding: libBlocksRuntime.so
Not embedding: libpthread.so.0
Not embedding: libutil.so.1
Not embedding: libdl.so.2
Already embedded: libswiftCore.so
Not embedding: libm.so.6
Embedding: libswiftGlibc.so
Not embedding: libgcc_s.so.1
Not embedding: libc.so.6
Already embedded: libswiftGlibc.so
Not embedding: libpthread.so.0
Not embedding: libutil.so.1
Not embedding: libdl.so.2
Not embedding: libm.so.6
Already embedded: libswiftDispatch.so
Already embedded: libdispatch.so
Already embedded: libBlocksRuntime.so
Embedding: libFoundationNetworking.so
Already embedded: libFoundation.so
Not embedding: libcurl.so.4
Already embedded: libswiftDispatch.so
Already embedded: libdispatch.so
Already embedded: libBlocksRuntime.so
Not embedding: libpthread.so.0
Not embedding: libutil.so.1
Not embedding: libdl.so.2
Already embedded: libswiftCore.so
Not embedding: libm.so.6
Already embedded: libswiftGlibc.so
Not embedding: libgcc_s.so.1
Not embedding: libc.so.6
Not embedding: libgcc_s.so.1
Not embedding: libc.so.6
Zipping .... done, size: 17M (unpacked 72M)
I finally managed to deploy a build made using swift lambda build --configuration release and it's working properly, so the problem only seems to happen with --configuration debug.
Activity
[-]Runtime error[/-][+]libicudataswift.so.65 missing[/+]helje5 commentedon Oct 16, 2020
Building the Macro example:
It looks OK, it seems packaged properly:
Could you run
swift lambda --verboseand post the output?alfavata commentedon Oct 19, 2020
Thanks for looking into this! I still haven't had time to retry, but here's the output you asked for:
alfavata commentedon Oct 21, 2020
Just realised that I never tried deploying a lambda built with
--configuration release- and the output ofswift lambda buildseems to be quite different with--configuration debug:[-]libicudataswift.so.65 missing[/-][+]libicudataswift.so.65 missing using `--configuration debug`[/+]alfavata commentedon Oct 22, 2020
I finally managed to deploy a build made using
swift lambda build --configuration releaseand it's working properly, so the problem only seems to happen with--configuration debug.