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

Windows: Linking errors with libmccs_stubs.a #16

Closed
bryphe opened this issue Sep 18, 2018 · 3 comments
Closed

Windows: Linking errors with libmccs_stubs.a #16

bryphe opened this issue Sep 18, 2018 · 3 comments

Comments

@bryphe
Copy link

bryphe commented Sep 18, 2018

We're using this project on esy as part of our solver infrastructure: https://github.com/andreypopp/esy-solve-cudf , and it works great! We're now working to enable this solver on Windows, however, and we hit a linking error when building that esy-solve-cudf project:

** Cannot resolve symbols for C:/Users/bryph/.esy/3_/i/opam__slash__mccs-1.1+8-e4af6af7/lib\mccs\libmccs_stubs.a(lexagregate_combiner.o/
notuptodate_criteria.o/
removed_criteria.o/
):
 _ZTVN10__cxxabiv117__class_type_infoE
 _ZTVN10__cxxabiv121__vmi_class_type_infoE

It looks like these are RTTI symbols.

@bryphe bryphe changed the title Windows; Linking errors with libmccs_stubs.a Windows: Linking errors with libmccs_stubs.a Sep 18, 2018
@dra27
Copy link
Member

dra27 commented Sep 18, 2018

You need a patched flexlink to support C++ linking - the patch is in the AppVeyor script (sorry, awkward
to do the link from my phone)

@bryphe
Copy link
Author

bryphe commented Sep 18, 2018

Thanks @dra27 ! Got it - I'll test it out and see if that fixes my issue. 👍

@bryphe
Copy link
Author

bryphe commented Sep 19, 2018

Confirmed it's fixed when I brought in your PR ocaml/flexdll#48 for flexdll - no other compiler flags needed. Thanks again @dra27 !

@bryphe bryphe closed this as completed Sep 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants