brandon s allbery kf8nh

`cabal-tests` hates AArch64 for some reason. Presumably one of @jasagredo's PRs fixes it, since it works on `master`, but I'm not going to fight with it right now.

This looks to me a lot like a cabal v1 workflow (`cabal [v2-]configure` edits `cabal.project.local`, it does _not_ configure a build). It probably wants to become a `runghc Setup.hs` workflow...

If there's a bug, it's that cabal 3.10.3 might have allowed (and possibly done unexpected things with) `v1-build` parameters given to `v2-build`.

If you have an existing `cabal` binary, you don't need to do anything special; just `cabal-boot build cabal` and `cp $(cabal-boot list-bin cabal) targetDir`, since there are no data files...

Perhaps https://github.com/haskell/clc-stackage would be of help here?

Pretty sure it does, and that's why `safeGetWindowAttributes` is in `Prelude.hs`. (I have certainly seen apps create and withdraw windows before we can manage them,)

Do you happen to know whether cabal-install-solver needs to be included here, since it's a library? My assumption is that it's internal and as such has no _public_ API to...

Also, this is very much WIP as I sort out what's needed (and deal with weirdshit like the fact that I somehow got a byte order mark the first time,...

Just made the current API dumps into artifacts, since not everyone will have an Ubuntu box to run `print-api` on and sufficiently large changes would be a PITA working from...

Originally I was thinking 9.4.8 for consistency with GHC_FOR_RELEASE, then discovered that wasn't supported so I bumped it. I could do it again with 9.10.1 if that's preferred.