On Sat, Apr 5, 2014 at 1:34 PM, Matthias Kilian
BTW: I already thought about amending haddock with a little autoconf (or similar) goo to get rid of ghc-paths...
Please, no! I'd love to abolish autoconf as much as possible! And, I don't see the reason for it. Or, for that matter, this particular package.... If we wanted to remove the dependency on the package, we could just include the one file in the haddock source tree. NOW - that file, GHC/Paths.hs, exports four paths that it gets by using CPP, and relying that GHC will supply some #defines at CPP time. However, we built HP from a bindist of GHC. And that bindist includes (am I wrong?) an already built haddock.... which means that haddock was built with a ghc-paths that was compiled... at the time the bindist was made. But that is the wrong environment! Those paths are all wrong for when we build the platform because we take the binddist, configure it for a particular target environment, and make install it. And that target may very well configure it for different locations. So... my thinking is that I probably have to build haddock, and ghc-paths, afresh, and will need a way to build and use ghc-paths for building haddock, without bundling it in the platform.