Note that in the current 1.22 branch, the --{en,dis}able-executable-profiling option (as well as {en,dis}able-library-coverage) was added back in order to be backward compatible. So these problems should not appear with the final release of 1.22. Regarsd, Erik On Sun, Jan 18, 2015 at 4:03 PM, Thomas Tuegel wrote:

On Sat, Jan 17, 2015 at 7:17 PM, Michael Jones wrote:

...

Using cabal 1.22 for some reason does not like —enable-executable-profiling. I am working on a rebuilt machine that had 1.18 from the distribution, with 1.22 installed afterwards. I found a little info on people having this problem, but I failed to fix the problem.

Note than the library profiling option is accepted. Only the executable fails.

Is there any know way to start with platform 2014 with GHC 7.8.3 and install cabal 1.22 and can use this option? _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

In Cabal 1.22, --enable-executable-profiling was renamed --enable-profiling because it is not actually possible to enable executable profiling safely without also enabling library profiling.

-- Thomas Tuegel _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe