make(1) file structure design/usage docs ?

[David Holmes]

On 11/07/2014 2:09 AM, pointo1d wrote:
> Hi all ,
>
> Could anyone tell me if there's a tie in between the
> --with-import-hotspot & --with-boot-jdk options, I ask purely because,
> although I can run a successful truly vanilla OJDK build, all attempts
> fail if I attempt to use either, or both of, the --with-import-hotspot
> &/or --with-boot-jdk options - the build consistently fails as follows...
>
> ## Starting jdk
> make[2]: *** No rule to make target
> `/home/dpointo8/work/repos/Mercurial/ojdk8.datum/build/linux-x86-normal-server-release/corba/dist/lib/classes.jar',
> needed by
> `/home/dpointo8/work/repos/Mercurial/ojdk8.datum/build/linux-x86-normal-server-release/jdk/classes/_the.CORBA.classes.imported'.
> Stop.

Check earlier in the build log to see why the corba classes.jar didn't 
get built.

> Moreover, more in hope than expectation, could anyone tell me if there
> is any documentation on the new i.e. autoconf based, make file structure
> and the way it knits together ? If I try an IBM variant build (using our
> hotspot & boot JDK), I always get a fatal error whereby the build fails
> to find the file jdk/classes_security/_the.BUILD_SECURITY_batch.tmp -
> hence my question about the structure of the make files.

This probably relates to the assumption that !OPENJDK == Oracle JDK. Do 
your builds set OPENJDK or not? There was a long thread on this not that 
long ago.

David

> TIA ,
>