On Wed, 21 Oct 2009, Stathis Kamperis wrote: > 2009/10/21 Saifi Khan <[email protected]>: > > Hi: > > > > Is there a difference between 'make' and 'bmake' on DragonFly > > BSD 2.4.1 ? > > > make is "our" make utility which belongs to our base. It's the very > same make utility that is used to build world and kernel or to > checkout the git src repository when you type 'make src-checkout' > inside /usr. make(1) can only parse our own Makefiles. > > Pkgsrc on the other hand needs the netbsd's make utility (netbsd is > the "native" platform of pkgsrc, so to speak). Therefore, we bootstrap > netbsd's make which results in "bmake" and use that to interpret the > pkgsrc's Makefiles. >
Statis, thank you for your reply. . In the directory test/amd64/, when a 'make scratch' is done, how are the different make's dynamically invoked ? eg. qemu and gcc44 are compiled using gmake openssl is compiled using bmake perhaps the master 'make' ie. the one running the test/amd64/Makefile is DragonFlyBSD make. . Is it correct to assume that other than 'pkgsrc' builds, there is no other role of 'bmake' in the DragonFlyBSD code base ? . Any source code/patch contributed to DragonFlyBSD project - kernel - userland tools must compile cleanly only with 'make' ie. DragonFly make ? . DragonFly BSD native make utility is the directory usr.bin/make/ . Is it correct ? thanks Saifi.
