I've traced some troubles to a problem with GHC's response to the -clear-package-db and -package-db flags. I would very much like to know if others can duplicate this issue. All that is needed is for you to try the following commands, or whatever variations may be appropriate for whatever ghc versions you have installed on your system: ghc-pkg init /tmp/empty-package-db ghc -clear-package-db -package-db /tmp/empty-package-db/ -v ghc-9.0.1 -clear-package-db -package-db /tmp/empty-package-db/ -v ghc-8.10.7 -clear-package-db -package-db /tmp/empty-package-db/ -v On my system at this present moment, ghc-8.10.7 respects the commands, but ghc-9.0.1 does not. The output from the `-v` options show what's happening: if GHC finds any packages that are *not* "wired-in," then something is broken. As examples, I attach the sample outputs from my own system. I think the issue is being caused by something mysterious in my filesystem. Last Friday, ghc 9.0.1 was respecting those flags. But today it is not. Before I try to figure out what is going on, I would *very* much appreciate learning if anyone else can duplicate the issue. Please try running GHC with an empty package database and let me know what happens. Norman