Claus
Thanks for the suggestions. We've uploaded your ghc-depends file, and
I've updated the building instructions to take account of your
suggestions.
would you like to look through the revised story to check you believe
it, and that nothing out of date or unnecessary is included? Here's the
stuff
http://research.microsoft.com/%7Esimonpj/tmp/building
Do make changes direct in CVS. Or send diffs
Simon
| -----Original Message-----
| From: Claus Reinke [mailto:[EMAIL PROTECTED]
| Sent: 15 May 2005 19:41
| To: Simon Peyton-Jones; [EMAIL PROTECTED]
| Subject: Re: Win32 build of ghc from cvs failed; also 6.4 source
distribution
|
| Simon
|
| some of the points have already been addressed in other ways, eg.
nightly
| mingw builds are there now, thanks to Sigbjorn, the point about adding
| GLUT is in the cvs version of the guide, but not in the online one,
Simon M
| changed build.mk as suggested, the many warnings are still there.
|
| the vague info about possible interferences should probably not go
into
| the building guide (I wanted to put it in the mailing list archives,
for
| desparate googlers, and in case anyone could see a possible reason for
| such conflicts, but I've seen that particular cygwin installation
stall on
| other occasions, so I can't be certain of the precise causes).
|
| I did however make a note to pay closer attention the next time I'd
build
| ghc on a new machine, especially wrt to cygwin dependencies, and that
| happened this weekend (see separate emails). For instance, it turns
out
| that there is a fairly simple way to make "cygwin-profiles", if you
want
| to. and, at least for just building ghc, there seems to be no need to
fiddle
| much with mingw/cygwin anymore (though I realise your guide has to
| cover all possible configurations, changes over time, and enough info
| that one might have a chance to adapt it if anything goes wrong).
|
| a few concrete points in the building guide seem to be wrong, though,
| or could be updated:
|
| 0. Alex, Happy, Haddock, are now part of the nightly builds and ghc
| mingw snapshots, which are needed to build cvs ghc anyway,
| available at http://www.haskell.org/ghc/dist/stable/dist/. (13.4)
|
| 1. "On Cygwin, do not add any of the mingw binaries to your path.
| They are only going to get used by explicit access (via the
--with-gcc
| flag you give to configure later). If you do add them to your path
you
| are likely to get into a mess because their names overlap with
Cygwin
| binaries. " (13.4)
|
| I tried that without installing any cygwin compilers/linkers, and
| configure couldn't find 'ld'. So it would seem that by following the
guide,
| I've been using cygwin's ld with mingw's gcc in earlier installations.
| prefixing the mingw PATH for the build seems safer?
|
| 2. cygwin's default ash seems to work just fine - no need to replace
it
| with bash for the build. I found only one script that needed bash,
| and that can easily use #!/bin/bash. (13.2)
|
| 3. gcc,ld are now used from mingw, not from cygwin. (13.2)
|
| cheers,
| claus
|
| ----- Original Message -----
| From: "Simon Peyton-Jones" <[EMAIL PROTECTED]>
| To: "Claus Reinke" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
| Sent: Wednesday, April 27, 2005 12:52 PM
| Subject: RE: Win32 build of ghc from cvs failed; also 6.4 source
distribution
|
|
| Claus
|
| Thanks for this feedback. If you can turn any of it into specific
| changes in the building guide I'd be (more than) happy to add them.
| E.g. new paragraphs, explanations, warnings etc.
|
| Simon
|
| ..
| | just so that I don't always write about builds that fail:-)
| |
| | I successfully built ghc head on win xp, with Monday's cvs,
| | and since my machine was rebuilt, with last week's cygwin
| | (out of curiosity, I did not exclude hslibs). Btw, I hope I'm
| | not spilling any secrets when I say that Sigbjorn has a nice
| | script for making movable tar-balls for windows without msi,
| | right there in cvs. Nightly windows builds and snapshots,
| | anyone?
| |
| | I noticed a few oddities:
| |
| | - cygwin doesn't give you a selection of "profiles", so when
| | I reinstall cygwin, I always have to modify the default
| | selection of packages for my purposes, mostly making sure
| | that all the tools I need will be included. I do not usually
| | have to do any funny stuff like replacing sh with bash!
| |
| | - the online building guide seems not to have been updated
| | with the cvs changes? I once again forgot to add GLUT
| | to MSYS the first time round..
| |
| | - at first, configure got hung up at various points (just
| | stalled, not returning or doing anything). since one of the
| | points was between x11 and hgl, I uninstalled all x11-related
| | stuff from cygwin before restarting the whole process. I
| | also uninstalled any mingw-related things to avoid any
| | accidental conflicts between cygwin's mingw and msys
| | mingw. after that, configure got through as expected.
| |
| | - apparently, I installed only part of the doc-processing tools
| | in cygwin, so configure gave me a message that some
| | conversions won't be possible. as I only wanted html,
| | that looked ok to me, but when doing the distribution
| | stuff, hslibs/docs suddenly tried to convert docs without
| | having the tools available - I just commented out that part.
| |
| | - it would be helful if the mk/build.mk.sample corresponded
| | to the default settings (with useful options in comments).
| | when having to add BIN_DIST=1, I naively copied and
| | modified that file, and was surprised by the amount of
| | work that was done after.
| |
| | - there was an absolutely amazing amount of warnings
| | generated in the process.. how do you ever find the
| | important ones in there? I'm often not good at going
| | for warning-free code myself, but I do recall that as
| | a pragmatically important invariant:-)
| |
| | As always, when it works, your build process is amazing
| | (have you recently counted the files in even the partial
| | fptools tree needed for ghc?-).
| |
| | cheers,
| | claus
| |
| |
| | _______________________________________________
| | Cvs-ghc mailing list
| | [EMAIL PROTECTED]
| | http://www.haskell.org/mailman/listinfo/cvs-ghc
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc
