>>>>> "rif" == rif <[EMAIL PROTECTED]> writes:
rif> I've now built a basic core using the 04-2004 sources and 04-2004
rif> binary. In terms of clarity, as far as I know, the only documentation
Very good!
rif> to look at is the README file in /src/tools/. It might be worthwhile
rif> explicitly mentioning there that linux users want to use the
rif> linux_gencgc rather than the linux option (I don't even know what this
The updated README says you don't have to give the extra args to
creat-target.sh and will guess appropriate values. For linux, this
will be linux_gencgc.
linux_gencgc enables gencgc generational GC. Plain linux is, I think,
the old cgc GC. I don't think anyone runs that version anymore.
rif> means); this is not clear a priori. There is also a paragraph in the
rif> README (lines 200-205) which states:
rif> IMPORTANT: You will normally have to modify the sample setenv.lisp
rif> file, to include code that puts at least a minimal set of features
rif> onto the list (use PUSHNEW and/or REMOVE). You can use the current
rif> set of *features* of your lisp as a first guide. The sample
rif> setenv.lisp includes a set of features that should work for
rif> Linux/x86.
I've fixed this somewhat already. It says leave setenv.lisp alone
unless you want to change something. You'll get whatever features
are in the lisp you used to build from.
rif> This paragraph makes it seem that maybe you're OK as it stands on
rif> Linux, but if you go look at the setenv.lisp you get after running
rif> create-target.sh, you see towards the top a line "Specific features
rif> that most people want:", and then a bunch of things commented out. To
I'll try to clean this up a bit to. This was true when it was
written, but cmucl is a little smarter now about figuring out the
feature set from the exising lisp without having to explicitly set
them.
rif> Now that I have a lisp.core, and I can say
rif> ./linux/lisp/lisp -core ./linux/lisp/lisp.core -noinit -nositeinit
rif> What do I have to do to finish (i.e., make this functionally
rif> equivalent to the CMUCL binary I started with)? If I try taking away
Ok, the README isn't too clear. There are a few steps you still need
to do:
1. Run src/tools/build-utils.sh to get Gray streams, simple-streams,
CLX, CLM, and Hemlock built.
2. This is optional, but I do this, just so I have a saved version of
what I built. Run src/tools/make-dist.sh to build 2 tar files.
These are equivalent to what you would find in the snapshots,
experimental, and release directories.
3. Use these tarballs to install them on your system, wherever you
want them to go.
I'll add this to the README.
Ray
