From: Daniel Lazarenko <danielo@opera.com>
To: wireguard@lists.zx2c4.com
Subject: Xcode 15 wireguard-apple build errors
Date: Mon, 7 Aug 2023 10:15:32 +0200 [thread overview]
Message-ID: <CAL77Jid=hbH6fQw1cWJW+VifyQ-+9-VORpuO=5R+uGDR5Yu8ow@mail.gmail.com> (raw)
Hello. We're using wireguard-apple for an iOS app. We're using this
library in production, it works as expected built with Xcode 14.3, but
we'd like to start testing the app on Xcode 15 to look for potential
breakage before iOS 17 goes live.
With the latest Xcode 15 beta 5, linking WireGuardKitGo library to the
WireGuard Network Extension target produces an error:
Initializer pointer must point to start of function (no addend) in
'.../Library/Developer/Xcode/DerivedData/MyApp/Build/Products/Debug-iphonesimulator/WireGuardKitGo.framework/WireGuardKitGo[arm64][2](go.o)'
and a warning:
'.../Library/Developer/Xcode/DerivedData/MyApp/WireGuardKitGo.framework/WireGuardKitGo[arm64][2](go.o)'
has malformed LC_DYSYMTAB, expected 61 undefined symbols to start at
index 4624, found 73 undefined symbols starting at index 15
Is it a known issue? Are there any existing fixes or clues to help
fixing the problem?
reply other threads:[~2023-12-20 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL77Jid=hbH6fQw1cWJW+VifyQ-+9-VORpuO=5R+uGDR5Yu8ow@mail.gmail.com' \
--to=danielo@opera.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).