Joshua Gatcomb wrote:
> I was hopeful that since this is the same architecture (the same machine
> even), that I would be able to proceed as outlined above.
Yes, it should be possible to go this route.
You're building a stage 1 compiler that is a mingw binary, producing cygwin
executables, i.e. host=mingw, target=cygwin. The configure script doesn't
understand cross-compilation, but you should be able to edit mk/config.mk after
configuration to set up the right host/target values, and then build away. I'm
sure you'll have to fix a few things along the way - this isn't something we
test on a regular basis (in fact, ever).
I accidently only replied to you on the first message Simon, so please forgive the duplicate.
Prior to even posting to the list, I followed the instructions outlined in
http://www.haskell.org/ghc/docs/latest/html/building/sec-porting-ghc.html#unregisterised-porting
The issue is that the dependency check wants the compiling ghc (mingw) to have the "unix" package. This is what I can't see how to get around.
Insights appreciated.
Cheers,
Simon
Cheers,
Joshua
a.k.a. Limbic~Regoin
_______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
