-
Notifications
You must be signed in to change notification settings - Fork 31
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
Unsupported relocation kind 0003 for __GSHandlerCheck in libcamlrun.lib(intern.obj) #29
Comments
This is a SEH relocation. It appears because the I decided to not implement this relocation because it is not clear to me how exactly that works, and given the high effort required for verifying a code path that in all likelihood will never be invoked, I opt to not risk including a broken implementation in flexdll. |
The workaround does not work if one wishes to link with the |
I've not seen this - is it still the case and is there an easy repro case? |
@dra27 I don't see any reason this would be fixed. As for the repro case--sure, as described in the first comment, building OCaml using VS2015 and the default Makefile.config is enough IIRC. |
I've been building x64 4.03.0 and 4.04.0 with VS2015 with no problems for ages - including all the work I'm presently doing. Do you see the same thing with trunk? |
OK, I will try again soon. |
I encountered a similar issue when compiling zarith with the VS2015 and used |
Just capturing for myself that I am getting this problem; don't have the time to investigate this properly. Much more time-consuming since this only appears on GitLab CI/CD. But it does seem clear that we shouldn't be ignoring valid relocations, regardless of how they are triggered. ProblemI recently switched to Errors:
and
|
PR #141 has the fix. |
Work around ocaml/dune#8643, but hit ocaml/flexdll#29
I'm getting this when building OCaml 4.03.0 for x64 with bootstrapped flexlink and Visual Studio 2015. The relocation kind is
IMAGE_REL_AMD64_ADDR32NB
. I have not yet investigated exactly what that means.The text was updated successfully, but these errors were encountered: