Yes, I know this is hackers only territory, but does it have to be made
deliberately difficult? I'm just trying to do this on a fresh machine and
while there's nothing especially difficult (not one tenth as bad as the
first time I did it . . .) the following are annoying:
(1) The repository is very puritanical about having to have autoconf and
happy installed. Since the chances of my wanting to muck about with the
configuration file/GHC parsers are nill, why not include the configure
script and Parser.hs/ParseIface.hs in the CVS repository. Also modify
the configure script so it doesn't fall over if it can't find happy,
but instead (if anything) prints some warning. The normal make mechanism
will then detect if Parser.y/ParseIface.y get modified.
(2) (cycle ["why","oh"]) are special GHC flags supplied for
particular files (eg
parser/Parser_HC_OPTS += -Onot
)
put before the GHC flags in HC_OPTS supplied for everything else?
This means I can't use them to compile the parser without optimisation,
but everything else with.
