<div dir="ltr">Yes, exactly.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 April 2014 22:03, Herbert Valerio Riedel <span dir="ltr"><<a href="mailto:hvr@gnu.org" target="_blank">hvr@gnu.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 2014-04-10 at 06:00:43 +0200, Vivian McPhail wrote:<br>
> Indeed.<br>
><br>
> It was using the wrong cabal-install version.  Even though I had installed<br>
> the newest cabal-install I needed to restart the xterm I was working<br>
> in.<br>
<br>
</div>Lemme guess, you're using Bash, and you installed cabal-install into a<br>
new location; however Bash caches the paths of called executables, see also<br>
<br>
 <a href="http://unix.stackexchange.com/questions/5609/how-do-i-clear-bashs-cache-of-paths-to-executables" target="_blank">http://unix.stackexchange.com/questions/5609/how-do-i-clear-bashs-cache-of-paths-to-executables</a><br>

</blockquote></div><br></div>