Skip to content

Fix configure: Define the CAML_SAFE_STRING variable when force-safe-string is on#9117

Merged
dra27 merged 4 commits intoocaml:4.10from
kit-ty-kate:4.10
Nov 14, 2019
Merged

Fix configure: Define the CAML_SAFE_STRING variable when force-safe-string is on#9117
dra27 merged 4 commits intoocaml:4.10from
kit-ty-kate:4.10

Conversation

@kit-ty-kate
Copy link
Copy Markdown
Member

While testing all packages in opam with OCaml 4.10 I was surprised to see that some old versions of some packages that I expected to fail (due to using the wrong C type for the string type – char* instead of const char*) did not fail.

This PR fixes the mistake I made in #1859, where I forgot to move the definition of CAML_SAFE_STRING to the other side of the if in the configure script.

This is a PR for the 4.10 branch but this should also be ported to trunk. Let me know if I should've done this the other way around.

@dra27 dra27 merged commit 9e3668a into ocaml:4.10 Nov 14, 2019
@dra27
Copy link
Copy Markdown
Member

dra27 commented Nov 14, 2019

Thanks, @kit-ty-kate and good spot for suspicious passes in the CI!

@dra27 dra27 mentioned this pull request Nov 14, 2019
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 this pull request may close these issues.

2 participants