chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] current cvs error?


From: Felix Winkelmann
Subject: Re: [Chicken-users] current cvs error?
Date: Fri, 13 Jun 2003 09:22:10 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530

Peter Keller wrote:

I have a comment about this part of the README.CVS file:

---
6. To generate the .c files needed to build the bootstrapped compiler,
   you must supply the full path to the Chicken compiler you built in
   step 2.

    $ gmake CHICKEN=/home/yourname/chicken-X.YYYY/dist/bin/chicken

This command will cause the entire system to be built using the
compiler you installed from the source snapshot. Never mind those warnings.
---

It turns out this is not entirely true. You need to actually do this:


$ gmake CHICKEN=/home/yourname/chicken-X.YYYY/dist/bin/chicken \
                CSI=/home/yourname/chicken-X.YYYY/dist/bin/csi

I say this because I had installed the bad bootstrapped version of chicken
into my /usr/local dir, and then when I built a cvs chicken version the
build system used whatever 'csi' it found in my path, not the one from
the bootstrap version of chicken I was relying on. The csi in my path
was bad, thereby preventing the recompilation from succeeding.

Yes, I'm sorry about this. Sven actually told me about this
problem a few days ago, and I simply forgot.


So, I propose changing the build slightly to make a BOOTSTRAP_PATH
Makefile variable which defaults to ./, but when you set it on the command
line, you use whatever bootstrapping executables you need(chicken, csi,
etc) as defined from that path.

Then the directions would say this:
$ gmake BOOTSTRAP_PATH=/home/yourname/chicken-X.YYYY/dist/bin

Sound reasonable?


Good idea. I hope to get near my machine at home this weekend and
fix it according to your proposal.


cheers,
felix






reply via email to

[Prev in Thread] Current Thread [Next in Thread]