ghc head on windows: gcc.exe: installation problem, cannot exec `cc1': No such file or directory

[Claus Reinke]

>>>    [1] Cabal should really pass -B to any direct calls to ghc-internal gccs
>>>    [2] ghc should preserve gcc's internal layout when including it, so that
>>>        prefix options work as well:
>>>    [3] ghc should tell its internal gcc where its subprograms are, so that
>>>        no extra -B is needed
> We already have a patch to sloving hsc2hs's gcc path problem by that way. [1]
> http://www.haskell.org/pipermail/cabal-devel/2008-September/003832.html

Thanks for the pointer, shelarcy! But looking through cabal-devel,
there seem to be several variants of similar patches floating
around, the latest requiring other changes to cabal?

Since there are ghc installations out there that do mutilate
their internal gccs, both cabal and ghc have to add -B for
now[1]. For future ghc releases, wouldn't it be better to keep 
gcc intact [2], so that gcc can find its pieces on its own, being
no different from any other gcc, and those special cases in 
ghc and cabal can disappear?

> Please test this patch and report result to Duncan. I think he 
> is wanting to know result to apply correct patch.

Which patch to test, Duncan? Or will the latest version appear
in ghc's cabal soon now?

Claus