Do we really need hscolour when using haddock with --hyperlinked-source? Also, a section on building for development (which is what I believe the current instructions are aimed at) would be nice!
I very much welcome this clean up! Cheers, Adam > On 29 Apr 2016, at 02:24, Carter Schonwald <[email protected]> wrote: > > i also added mention of invoking ulimit before make to work around a current > bug in haddock resource usage when generating hyperlinked-source files for > all of ghc :) > > On Thu, Apr 28, 2016 at 8:22 PM, Carter Schonwald > <[email protected]> wrote: > 1) done > > 2) steps 12,13,15 are specific to git checkout, step 14 is still necessary! > a) hyperlinked-source is not enabled by default for the boot libs and ghc > source, which is AMAZING to have > b) buliding the pdf version of the user guide isn't enabled by default > c) if you have gmp lib somewhere installled in userland, ghc will by default > pick that instead of doing in tree gmp, and on mac if you want to share you > executables, that a no go! > d) unrelatedly, it seems that ghc build no longer includes the haddock manual > in html/pdf form as it used to > > 3/4) i think we shouldn't make any assumptions about the path and what > gcc/clang is where / shows up first, or at least that choice should be > explicit :), good point on the --with-nm idea > > 5) i prefer not mentioning sudo ever in directions, and i actually these days > install my various ghc versions into paths like ~/.install-ghc/$GHCVERSION > :), and certain prefixes may or may not be locked down on recent osx it > seems :) > > On Thu, Apr 28, 2016 at 7:25 PM, George Colpitts <[email protected]> > wrote: > Thanks for working on this! > > fwiw, my comments: > > • It would be good to provide a link to the current doc so we can > compare with that. > • Steps 12, 13, 14 and 15 are only necessary if you are building from > a fresh git checkout, not necessary if you're building from source tree > tarball from a release candidate , right? > • If your path is set so that the gcc you want to use is one it > specifies than you don't need either of the two (!!) step 16s, at least in my > experience. > • For step 17, in my experience, I don't have to use --with-gcc .... > For with-nm the best way to specify is as Brandon wrote --with-nm=$(xcrun > --find nm-classic) > • After either 18 or 19 it would probably be good to mention the option > of doing sudo make install > Thanks for jumping on this, the old doc definitely needs updating > > Cheers > George > > On Thu, Apr 28, 2016 at 7:24 PM Carter Schonwald <[email protected]> > wrote: > Woops forgot to link them this morning > > https://gist.github.com/cartazio/32038db09222a2aac767cb5c03b406c6 > > Feedback would be appreciated. > And still need to mention cabal install hscolour :) > > Pardon the noise and feedback would be appreciated! > > On Thursday, April 28, 2016, Carter Schonwald <[email protected]> > wrote: > Hey all: > I've drafted some hopefully cleaner Mac build directions and I'd love some > feedback on them > > Nb: I think I forgot to mention the cabal install hscolour step, I'll add that > > -Carter > > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
