Stuart Henderson <stu@spacehopper.org> writes:

>> And I've already mentioned these in previous emails (with patches), but
>> just to clarify, in case it helps (since I don't know what opaque FILE
>> means, or how it relates to needing cross-compile scaffolding; sounds
>> like an abstract FILE pointer in C):
>
> There's a pending "flag day" ABI change in the base OS to make FILE
> pointers opaque, which IIRC means that all bootstraps in ports will
> need regenerating and quite likely without being able to use existing
> binaries.

I have a recipe for this "flag day" which I practiced with the previous
set of FILE patches (and emailed to you and a few others). It's fiddly
but not hard.

> I don't remember how far it impacted GHC but it's conceptually not that
> far from a cross-compile (i.e. compiler binaries need to be able to
> produce binaries that won't run on the same system type - though it's
> different versions of the same arch, rather than different archs).

Yeah, that's another way to do it. If we have a sure-fire way to
cross-build, I won't say not to that. So, Habib, you send a cleaned set
of patches I'll happily use the option. You could also push the git tree
somewhere, e.g. propose an MR to my tree on gitlab.

Thanks
Greg