[GHC] #2085: cabal uses haddock from hard-coded location

[GHC]

#2085: cabal uses haddock from hard-coded location
-----------------------------+----------------------------------------------
    Reporter:  Frederik      |        Owner:         
        Type:  bug           |       Status:  closed 
    Priority:  normal        |    Milestone:         
   Component:  Build System  |      Version:  6.8.2  
    Severity:  normal        |   Resolution:  wontfix
    Keywords:                |     Testcase:         
Architecture:  Unknown       |           Os:  Unknown
-----------------------------+----------------------------------------------
Changes (by duncan):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 If someone specifies a non-standard location using --happy-prog= then we
 have to remember that in the configuration somewhere. Even if the program
 is on the path we have to check that it does indeed exist, so that
 involves finding it and often running it to check its version. Then the
 choice is between remembering the unqualified or fully qualified path.
 There does not seem to be much to choose between the two, we somewhat
 arbitrarily pick the qualified path.

 I think other systems do this too, eg you'll see many build systems
 running /usr/bin/gcc even though they were only looking for gcc on the
 path at configure time. For example autoconf saves the path info in the
 Makefile, generated by ./configure.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2085#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler