Various cabal issues.

[rrnewton]

First, there was the issue that lead to separating test-atomic-primops

(TODO)

More recently, there are various different problems w cabal 1.20 and 1.22

For example, this with --run-tests on a profiling build in either cabal 1.20 or 1.22:

Loading package atomic-primops-0.8 ... linking ... done.
ghci-test.hs:18:16:
    cannot find normal object file ‘dist/dist-sandbox-a2a4e32d/build/template-haskell-atomic-primops/template-haskell-atomic-primops-tmp/TemplateHaskellSplices.dyn_o’

Vs this with a discrete cabal-1.20 test:

++ cabal-1.20 test --show-details=always
cabal-1.20: dist/setup-config: invalid argument

On 1.22.3.0, I'm seeing it complain about lack of configure when it just ran configure. And somehow it thinks the version of GHC has changed, when it should pick it up from the configure.

++ cabal-1.22 configure --with-ghc=ghc-7.6.3 --enable-tests -O0 --disable-library-profiling --disable-profiling --disable-coverage -fthreaded --ghc-options=-threaded
Resolving dependencies...
[1 of 1] Compiling Main             ( dist/setup/setup.hs, dist/setup/Main.o )
Linking ./dist/setup/setup ...
Configuring atomic-primops-0.8...
++ cabal-1.22 test --show-details=streaming
cabal-1.22: You need to re-run the 'configure' command. The version of Cabal being used has changed (was Cabal-1.20.0.2, now Cabal-1.22.3.0). Additionally the compiler is different (was ghc-7.6, now ghc-7.8) which is probably the cause of the problem.

But specifying the GHC version to cabal test doesn't help either:

Configuring atomic-primops-0.8...
++ cabal-1.22 test --with-ghc=ghc-7.6.3 --show-details=streaming
cabal-1.22: You need to re-run the 'configure' command. The version of Cabal being used has changed (was Cabal-1.20.0.2, now Cabal-1.22.3.0). Additionally the compiler is different (was ghc-7.6, now ghc-7.8) which is probably the cause of the problem.

But even if I remove all uses of --with-ghc, I still get the exact same error message above.

After tweaking it a few times I get the same missing ".dyn_o" failure on ghci-test.hs above when using a discrete cabal configure / cabal test per package. It's possible that now in cabal 1.20+, recombining test-atomic-primops into the atomic-primops library could work around this bug....