749606 – (ocaml-4.10) [Tracker] Breakage with OCaml 4.10

Bug 749606 (ocaml-4.10) - [Tracker] Breakage with OCaml 4.10

Summary: [Tracker] Breakage with OCaml 4.10

Status:	CONFIRMED

Alias:	ocaml-4.10

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Team for the ML programming language family

URL:
Whiteboard:
Keywords:	Tracker

Depends on:	749609 709646 749149 750977
Blocks:	ocaml-4.12
	Show dependency tree

Reported:	2020-10-17 01:26 UTC by Sam James
Modified:	2022-08-25 05:03 UTC (History)
CC List:	1 user (show)

See Also:	ocaml-4.09 ocaml-4.12
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sam James archtester

2020-10-17 01:26:18 UTC

OCaml 4.10 disabled unsafe-string unless it is specifically enabled at build-time of the compiler.

This is bug 737154 redeux as the fallout continues. Workarounds from that bug are unlikely to work here - we'll only be in luck with previous fixes if the actual code was ported.

Comment 1 Sam James archtester

2020-10-17 04:26:03 UTC

As Hank observed in bug 749149:
>Confirmed; ocaml-4.09 allowed forcing safe strings with ./configure --enable-force-safe-string, but 4.10 and up default to enabling it and require ./configure --disable-force-safe-string to get the old behavior back:
>In the meantime, either ocaml-4.1[01]* ebuilds could be updated to include --disable-force-safe-string (by default, or w/a USE flag, that these dev-ml/ packages depend on?)

So that's an option if we need to.