<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>Something like that yes.<br>
<br>
You're running runhaskell Setup.lhs and that loads and runs code from<br>
the Cabal library. The Cabal library depends on the process library<br>
which depends on the unix library. So by replacing the same version of<br>
the unix package you're breaking everything else which depends on it,<br>
including Cabal and thus runhaskell Setup.lhs.<br>
<br>
So the solution is to not do that. Don't re-install the exact same<br>
version of any of the core libs that come with ghc. Adding new versions<br>
is fine, replacing existing versions is not fine because it breaks all<br>
the other packages that were already built against that package.<br>
<font color="#888888"></font></blockquote><div> <br> But Duncan, let's suppose I build "unix" putting in a "local" directory with a different version number than the released version of "unix".<br>
<br> 1) How do I get the "local" package.conf built and populated?<br><br> 2) How do I get a test case to link against this experimental local version of "unix"? Is there a "--prefix" or something like that I pass on runhaskell Setup.hs build?<br>
<br>Regards, Vasili<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br>
Duncan<br>
<br>
</font></blockquote></div><br>