> I'm guessing I didn't do the b1 build right. The compiler it
> generated
> builds, but doesn't even run. Do I need to add the
> unregistered options
> throughout the build, or just in the library?
Just the libraries and the RTS in b1, and the compiler in b2. You can check
that things are w
On Tue, Oct 10, 2000 at 03:15:49AM -0700, Simon Marlow wrote:
> > I've got my x86 linux box ready to build some unregistered .hc files.
>
> You'll need two build trees. In the first tree, build the compiler as
> normal, and the libraries/RTS with -unreg -keep-hc-files-too. You should be
> able
> I'm considering taking some effort to port GHC to powerpc
> linux. The task
> seems moderately doable, given that GHC once ran on the powerpc
> architecture.
Cool! :)
> I guess as a good first question: should I start with 4.08.1,
> or should I
> venture off with the CVS tree. The driver i
I'm considering taking some effort to port GHC to powerpc linux. The task
seems moderately doable, given that GHC once ran on the powerpc
architecture.
I guess as a good first question: should I start with 4.08.1, or should I
venture off with the CVS tree. The driver in CVS seems to have been
w
