Skip to content
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

[Mono] Fix inconsistent linkage error in dynamic component build on Windows. #55142

Conversation

lateralusX
Copy link
Member

#54887 added MONO_COMPONENT_API to mono_gc_memmove_atomic.h, but that function is declared in two different headers, memfuncs.h and gc-internal-agnostic.h and the second one didn't use MONO_COMPONENT_API causing inconsistent linking errors on Windows when building dynamic components.

dotnet#54887 added MONO_COMPONENT_API
to mono_gc_memmove_atomic.h, but that function is declared in two
different headers, memfuncs.h and gc-internal-agnostic.h and the
second one didn't use MONO_COMPONENT_API causing inconsistent linking
errors on Windows when building dynamic components.
@ghost
Copy link

ghost commented Jul 4, 2021

Tagging subscribers to this area:
See info in area-owners.md if you want to be subscribed.

Issue Details

#54887 added MONO_COMPONENT_API to mono_gc_memmove_atomic.h, but that function is declared in two different headers, memfuncs.h and gc-internal-agnostic.h and the second one didn't use MONO_COMPONENT_API causing inconsistent linking errors on Windows when building dynamic components.

Author: lateralusX
Assignees: -
Labels:

area-VM-meta-mono

Milestone: -

@lateralusX lateralusX merged commit a2665c7 into dotnet:main Jul 6, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants