[ Ben sent me a copy of his build output. I'm sending the response to eros-port because others will surely have the same problem. ]
OK. The problem is that you followed directions. I'll go remove them so it doesn't happen again... :-)
Basically, I forgot to create a kernel configuration file for the DEFAULT kernel configuration. In consequence, the 'config.py' step failed and the kernel never got built. Contrary to the documentation, the EROS_CONFIG variable at the moment defaults to DEVEL. Because you set it explicitly you ended up with a bad build.
In point of fact, you got through the compile of the boot/ subtree, which means that the cross environment compiler is working correctly. This is quite a good thing!
A quick way to confirm the problem is to cd to eros/src/base/sys/, *remove* the EROS_CONFIG environment variable from your environment entirely (make sure it's not in your .cshrc, for example) so that it will default in the build, and type 'make install'. You'll know that the install is going correctly when two things have happened:
While you are actively doing work on EROS my recommendation is to run with EROS_CONFIG set to 'DEVEL' in any case. This causes the kernel debugger and symbols to be included in the kernel, and also causes the kernel to be compiled with assertion checking. This roughly doubles the size of the kernel (mostly due to symbols).
A real fix has also been applied in the tree -- the next time you run 'cvs update' you will get the DEFAULT configuration properly. For a quick fix, you can run cvs update by hand in build/lib/make and also in base/sys/arch/i486/conf. You should get two things:
DEFAULT, at the moment, is content-identical to DEVEL. When we are sufficiently stable this should change.
Sorry about this. Ah the joys of writing directions for evolving systems!