Re: [xmonad] Broken Xmonad after updates

I'm looking at that page, and aside from one slight documentation bug that doesn't really affect anything here it looks correct to me and shouldn't be able to get the wrong executable name unless something has gone wrong inside xmonad's compile logic. Although that also looks out of date: we support stack building directly, so xmonad should use essentially that build script itself when it sees a `stack.yaml` file. You probably want to use the latest version of the install documentation: https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-using-stack On Sun, Oct 22, 2023 at 11:11 AM Jan Detke wrote:

Brandon Allbery writes:

...

Essentially yes. Arch and derivatives insist on using dynamic linking, and you must rebuild your config after every system update to ensure it still works. We strongly recommend you use `stack` or `cabal` instead, and install `xmonad` and `xmonad-contrib` from Hackage. If you choose not to do so, see

https://wiki.archlinux.org/title/Xmonad#Problems_with_finding_shared_librari...

So I went the route of removing everything related to haskell, ghci and cabal from my system and followed the instructions of installing and setting up xmonad with stack. The installation went through and xmonad is recompiling under the usage of the given bash script (which invokes stack build). There are no errors given to me but I noticed that there is no 'xmonad-x86_64-linux' executable generated in my folder after running the script. In fact there is an executable created called '-lm' but I do not know if this is just an issue related to the filename or something else wrong here.

I followed these instructions on installing xmonad via stack: https://github.com/xmonad/xmonad/blob/883143fd5895e0da4ee8e50722e3011cf30e2c...

Can you help me out here?

Best regards Jan

-- brandon s allbery kf8nh allbery.b@gmail.com