prep-bin-dist-mingw supports to bundle GHC Windows binary distribution
with cc1plus.exe, now.
But prep-bin-dist-mingw assumes that GHC is build by MinGQ version 3,
Does anyone know whether or not this script is still used? It looks like
it contains a number of out-of-date values, and doesn't seem to be
called by the Windows nightly builds. I don't know about the Windows
installer.
Sigbjorn would be the right person to ask, I guess?
as a windows user, i have very much depended on prep-bin-dist-mingw, whenever
i want to convert my inplace GHC into something resembling the snapshots/releases.
i haven't done that for a while, because i tend to wait for the nightly builds to go
through without hitches, but i'd certainly miss that feature.
and i thought that whoever intoduced the recent version-in-path changes hasn't
gotten
around to updating the windows builds, which looked like the reason for the ongoing
failures in the nightly builds since then:
**** building compiler binary distribution ... failed.
**** canonicalizing mingw binary distribution tree... failed
(ghc-6.7.20070312 not found).
but if you say it isn't used anymore, what is the current recommended way to
create an installer-free bundle of a working self-compiled GHC on windows,
and why does the distribution stage keep failing?
once upon a time, i suggested to extract the relevant information from the
configure info, instead of the current hard-coded values/paths, but while it
is fairly easy to get info from GHC's configure
http://www.haskell.org/pipermail/cvs-ghc/2005-May/025075.html
that idea was somewhat naive - the real problem are the changes in
directory layout within gcc/mingw et al.
unless one can query gcc about its directory structure (??), the script
keeps having to be adapted by hand for different versions, which means
that someone has to decide that their build environment needs updating,
which isn't likely as long as it works, and that someone has to invest
time into figuring out what changes such an update implies for the script
(and i tend to dread updating my working system whenever someone
updates the script, because by the time that change reaches me, i might
update to a version of gcc/mingw with new problems/dependencies..).
but of course, there are new windows GHC users, and those who like
to keep their mingw/gcc uptodate, and that group doesn't like the old
values in the script.. perhaps one could accumulate known mingw/gcc
configurations, and make the script select the appropriate one based
on version info..
claus
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
