Re: text relocations... graphics/ocaml-cairo won't build on 2026Q2

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Greg Troxel <gdt%lexort.com@localhost> writes:

> Brad Spencer <brad%anduin.eldar.org@localhost> writes:
>
>> /lhome/WORK/graphics/ocaml-cairo/work/ocaml-cairo-0.6.5/_build/default/src/../config/discover.exe: Cannot write-enable text segment: Permission denied
>
> I see this too.
>
> Ideas:
>
>   `sysctl -w security.pax.mprotect.enabled=0` lets the package build.
>   Not recommending that, but a data point.

I suspected that there was a sysctl setting that would allow this to
build, but wasn't sure which one and didn't want to start flipping
things off at random.

>   Almost certainly, some paxctl invocations will help (+m probably),
>   patched into the build after the program is compiled and before it's
>   used in a way that triggers this error.  Basically turning off
>   mprotect for just this program.

That is my understanding.  I believe that I noted that packages will do
this from time to time.

>   Probably there's a hard path to actually fixing this correctly.  It's
>   a lonely path; ~nobody uses i386 and ~nobody uses ocaml, with the
>   intersection of those and NetBSD being perhaps just you.   I know you
>   know this already :-)

Well, yes...  32 bit i386 is getting more lonely with each passing year.
I don't run it directly on any physical hardware any more, but it works
pretty well in Xen as a PVH guest using the GENERICPAE kernel and take
up much less disk and memory than NetBSD/amd64.

I wasn't actually using ocaml directly, it was a part of the unison
build, which I do use.  In particular, the lablgtk option in unison
pulls in x11/ocaml-lablgtk which is what ocaml-cairo uses.  Since I
don't need lablgtk support in unison, I disabled it.

>   Note that NetBSD/amd64 does not have this problem.

I am not really suprised.




-- 
Brad Spencer - brad%anduin.eldar.org@localhost