Open Fuuzetsu opened 7 years ago
@Fuuzetsu, I am working through issues - including ones raised some time ago. With the current version of Stack, it looks for haddock
in the same directory as the directory containing the specified GHC executable.
Consequently, I have rephrased your issue as a feature request.
General summary/comments (optional)
I'm trying very hard to get stack to use a patched version of haddock. There is no flag that I can find which allows me to do this.
stack build haddock
with haddock in local dependencies seems to do the right thing but thenstack build
walks all over it. I do not see any way to pass through--with-haddock
toconfigure
phase or any other usual tricks.Steps to reproduce
In stack.yaml I have the following which is a monkey-patched version of Haddock (2.17.3.1.1).
As you can see
exec
picks the right version. I have this setup on a jenkins machine but there (slightly anonymised)Expected
Given the output of the above, when stack goes on to call
haddock
, I would expect my locally built 2.17.3.1.1 be used, not some system one.Actual
Why oh why?! And yes, it builds and sees the "right" version
but then during very next step it uses the system version (and build fails because that Haddock is unpatched).
Stack version
Method of installation
apt-get
likely.