Xmonad cannot find modules

euclio · 2017-10-03 03:55:33

I used to use the haskell-core repository, but I got frustrated by the breakages and I'm trying to move back to using the officially supported haskell packages in the community repo. However, I'm running into compilation errors on `xmonad --recompile`, after removing the haskell-core repo, similar to the errors described here: https://bbs.archlinux.org/viewtopic.php?id=195366

I've tried everything in the thread, including removing all haskell-related folders and completely reinstalling. Nothing has fixed it. Every reinstall leads me to the same errors.

Last edited by euclio (2017-10-03 03:57:53)

seth · 2017-10-03 07:59:48

similar to the errors

https://bbs.archlinux.org/viewtopic.php?id=57855

spider-net · 2017-10-03 11:45:35

I'm having the same issue but with xmonad and the packages provided by pacman.

Errors log: https://nopaste.linux-dev.org/?1162171
xmonad.hs: https://nopaste.linux-dev.org/?1162172
Output of pacman -Ql xmonad-contrib: https://nopaste.linux-dev.org/?1162173

Things I've tried:
- ghc-pkg reache --global (and without global)
- deleting .ghc/ folder.
- Reinstalling xmonad and xmonad-contrib
- Compiling xmonad.hs with the -dynamix flag.

Note: I don't have cabal installed.

seth · 2017-10-03 12:04:27

Tried

Use -v to see a list of the files searched for.

spider-net · 2017-10-03 12:17:08

Yes, this is the output: https://nopaste.linux-dev.org/?1162174

I can tell it can't find the proper files, but how do I fix it?

brianb · 2017-10-03 12:24:25

I'm getting the same errors ever since upgrading to xmonad-0.13-9. If I downgrade back to xmonad-0.13-8, I can recompile again just fine.

spider-net · 2017-10-03 12:33:39

brianb wrote:

I'm getting the same errors ever since upgrading to xmonad-0.13-9. If I downgrade back to xmonad-0.13-8, I can recompile again just fine.

Exactly, downgrading fixes the issue.

seth · 2017-10-03 12:36:59

And which files does that version test? ...

spider-net · 2017-10-03 12:42:43

The new version introduces this patch: https://github.com/anthraxx/arch-pkgbui … 6e757c024f referenced also here https://github.com/xmonad/xmonad/issues/86

seth · 2017-10-03 13:52:51

Which looks quite different from the replaced patch https://git.archlinux.org/svntogit/comm … 04025b8ea6

Last edited by seth (2017-10-03 13:53:03)

spider-net · 2017-10-03 14:04:29

The first link contains the changes made to the PKGBUILD, it adds the new patch. This is the relevant commit by felix: https://github.com/felixonmars/archlinu … dd4d838511.

Last edited by spider-net (2017-10-03 14:05:34)

ilikerackmounts · 2017-10-03 18:58:03

I'm getting these identical errors with regard to the shadowed dependencies.

Last edited by ilikerackmounts (2017-10-03 18:59:08)

spider-net · 2017-10-03 19:23:44

ilikerackmounts wrote:

I'm getting these identical errors with regard to the shadowed dependencies.

What happens if you downgrade xmonad? Does it get fixed?

ilikerackmounts · 2017-10-03 19:32:43

How do I do that without downgrading a ton of other packages? I tried using the last one from my package cache and it complained about some other haskell-x11* packages (but installed anyway). It still failed to work, though.

spider-net · 2017-10-03 19:34:51

ilikerackmounts wrote:

How do I do that without downgrading a ton of other packages? I tried using the last one from my package cache and it complained about some other haskell-x11* packages (but installed anyway). It still failed to work, though.

I just downgraded xmonad without no complaints. It's still not an acceptable fix.
Mmh, I dunno.

UPDATE: try updating xmonad-contrib, that fixed it for me.

Last edited by spider-net (2017-10-04 06:08:58)

brianb · 2017-10-04 08:29:47

I ended up uninstalling all-things-arch-haskell (xmonad, xmobar, ghc, etc.) and instead reinstalled them via stack. I wrote a step-by-step tutorial here for anyone interested.

ilikerackmounts · 2017-10-04 15:06:38

brianb - I ended up doing this as well, but I'd much rather use the arch maintained packages. This is frustrating.

brianb · 2017-10-04 15:10:09

ilikerackmounts wrote:

brianb - I ended up doing this as well, but I'd much rather use the arch maintained packages. This is frustrating.

Apparently, the latest update to xmonad-contrib (0.13-7) fixes things. I'm sticking with stack for now, so I can't confirm.

ilikerackmounts · 2017-10-04 18:47:32

Yes, I can confirm the latest update to xmonad-contrib fixed things. It was broken for well over a week, though. Given that users may or may not routinely run xmonad --recompile, it makes the issue substantially worse.

Arch Linux

#1 2017-10-03 03:55:33

Xmonad cannot find modules

#2 2017-10-03 07:59:48

Re: Xmonad cannot find modules

#3 2017-10-03 11:45:35

Re: Xmonad cannot find modules

#4 2017-10-03 12:04:27

Re: Xmonad cannot find modules

#5 2017-10-03 12:17:08

Re: Xmonad cannot find modules

#6 2017-10-03 12:24:25

Re: Xmonad cannot find modules

#7 2017-10-03 12:33:39

Re: Xmonad cannot find modules

#8 2017-10-03 12:36:59

Re: Xmonad cannot find modules

#9 2017-10-03 12:42:43

Re: Xmonad cannot find modules

#10 2017-10-03 13:52:51

Re: Xmonad cannot find modules

#11 2017-10-03 14:04:29

Re: Xmonad cannot find modules

#12 2017-10-03 18:58:03

Re: Xmonad cannot find modules

#13 2017-10-03 19:23:44

Re: Xmonad cannot find modules

#14 2017-10-03 19:32:43

Re: Xmonad cannot find modules

#15 2017-10-03 19:34:51

Re: Xmonad cannot find modules

#16 2017-10-04 08:29:47

Re: Xmonad cannot find modules

#17 2017-10-04 15:06:38

Re: Xmonad cannot find modules

#18 2017-10-04 15:10:09

Re: Xmonad cannot find modules

#19 2017-10-04 18:47:32

Re: Xmonad cannot find modules

Board footer