brandon s allbery kf8nh

It's right in the configure log in the initial report: ``` checking for X... libraries /usr/X11/lib, headers /usr/X11/include ``` Since configure has determined that (and this is correct on OS...

@larryhynes, while that is true, it's not really relevant; `/usr/X11` works fine and configure is clearly finding it and successfully using it. It's just not bothering to tell the actual...

What font are you trying to use? Note that if you were using an XFT font and then rebuilt xmonad-contrib without -fuse_xft, you will get this error because XCreateFontSet doesn't...

This used to work apparently, per https://github.com/xmonad/xmonad/issues/199#issuecomment-609433196; I don't know when it broke, and whether it was an xmonad/X11 change or a cabal (or Cabal) change.

And it turns out that the released version still builds fine. Are the instructions perhaps out of date and it takes more than just `autoreconf` to prepare the git version...

In fact this appears to work again with cabal-install 3.4. We may have to exclude cabal-install 3.2 from use for building, if possible.

I'm wondering if it's the OOM killer. I reproduced it again with a smaller image viewer, but things actually worked for a while until I tried to focus a window...

Github won't let me attach the typescript, even as a tar.gz. It is available as https://www.dropbox.com/s/qd2zk9p3omj6lbc/typescript.txt.tar.gz?dl=0.

Same failure with `cabal v2-build`. Interestingly, I get a different failure mode if I start out with an unpopulated `~/.cabal`, do a `cabal v2-update`, then attempt the same `cabal v2-build`....

It works if I use my existing `~/.cabal` (I have it bind-mounted so I can make it go away and come back easily; unfortunately `xmonad` is running from it so...