-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[libblocksruntime] The current version 0.4.1-2 seems to be missing export symbols #19743
Comments
The first failing build occurred 3 weeks ago, which coincides with this change: |
this change did nothing to the package. it's just metadata for website |
Yes, sorry, I didn't mean to imply that this change caused it. But there was a new build 3 weeks ago, and maybe some external script in some other package has changed. I downloaded the previous build (1) and looked in the dll contents. 0.4.1-2:
0.4.1-1:
|
FYI: we are unblocked, and can build again, by using another version of BlocksRuntime.dll |
Weird that package-grokker didn't catch this |
Package-grokker catches missing symbols for reverse dependencies. |
ah, right, we have no internal users. |
Did #19777 improve things? |
The
Also worth nothing that libobjc2 recently landed in msys2, which also includes a Blocks runtime. |
We have already resolved the problem by switching to our own build of this library, and I will not be able to spend the time necessary to switch back. |
Out of curiosity, which repository are you using to get the sources for libblocksruntime? |
From here: https://github.com/apple/swift-corelibs-libdispatch/releases |
we are about to remove old |
It was removed in 7aaaa112 and It's now provided by libdispatch package. |
Description / Steps to reproduce the issue
I'm building my project via github action / workflow, and get linking errors.
No related changes on my side.
The library is definitely getting linked, but symbols are not found.
I downloaded and inspected the dll file from the package, and it doesn't seem to have those symbols exported.
Expected behavior
There should not be any errors
Actual behavior
I'm getting linker errors
Verification
Windows Version
Microsoft Windows Server 2022 10.0.20348
MINGW environments affected
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: