Indeed. This is something I should add to the release notes.
Under normal conditions, what you want to be typing is 'make install'. As you say, later portions of the build depend on the installation of earlier portions of the build.
I went back and forth on this. Ultimately, I concluded that having the components in the base package built from the same headers and libraries and paths that non-base components would be built from provided an inherently useful regression test.
Note, please, that everything resulting from 'make install' will get installed under $EROS_ROOT. In my personal environment, EROS_ROOT is $HOME/eros, and my tree looks like
$HOME/eros/src build base legal doc etc...
> make: Entering directory
> g++ -fdefault-inline -fno-implicit-templates -g -fno-rtti
> -fno-exceptions -I../ -I/home/ben/work/eros/cross/include -Wall
> -Winline -Werror -c AppExit.cxx
> In file included from AppExit.cxx:17:
> ../erosimg/App.hxx:17: eros/target.h: No such file or directory
> In file included from ../erosimg/App.hxx:19,
> from AppExit.cxx:17:
> ../erosimg/Diag.hxx:16: eros/target.h: No such file or directory
> ../erosimg/Diag.hxx:17: disk/ErosTypes.h: No such file or directory
> make: *** [AppExit.o] Error 1
> Looks to me like this is depending on files installed in cross/include,
> but they can't be installed there until the build is complete... oops!
> There seems to be a lot of this, but this is the first instance.
> Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member
> Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/
> and Technical Director|Email: email@example.com |
> A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/
> London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/