The configure script has to be run. It generates a file `BuildConfig' (in the `current' directory) that is needed by the our Jamrules. Currently it doesn't contain that much, so for the time being you could create it manually. I don't have BeOS at hand right now. Under SuSE Linux it looks like:
FLOPPY_PATH ?= "" ; GCC_PATH ?= /usr/lib/gcc-lib/i486-suse-linux/2.95.3 ; BOCHS_DEBUG_HACK ?= 0 ;
Only the GCC_PATH has to be adjusted. Under BeOS it should start with `/boot/develop'. `dirname $(gcc -print-libgcc-file-name)' will tell you.