Date: Mon, 24 Apr 95 22:45 MSZ From: me@tartufo.pcs.dec.com (Michael Elbel) To: rgrimes@gndrsh.aac.dev.com Cc: hackers@FreeBSD.org Subject: Re: Any objection to adding a .undef(VARNAME) to make? Message-ID: <m0s3V0t-000Pa1C@tartufo.pcs.dec.com> References: <199504220356.UAA02180@freefall.cdrom.com> <199504220519.WAA00942@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In pcs.freebsd.hackers you write: >> Why do we use . instead of #? I've installed pmake on my system, >> but it's not a straight drop-in replacement for make due to this and >> other differences. >> >I do not have an answer for this, it was something done at CSRG. It would >be a major rework to change it though! Hmm, I'm confused: (17) uname -a FreeBSD dodo 2.0.950418-SNAP FreeBSD 2.0.950418-SNAP #1: Sat Apr 22 07:31:37 MET DST 1995 root@dodo:/1/curr/src/sys/compile/dodo i386 (18) cd /usr/src/usr.bin/make (19) grep -i pmake * Makefile.dist:pmake: Makefile.dist:cc *.o lst.lib/*.o -o pmake compat.c: *mode of PMake. Most of the special functionality of PMake dir.c: *of course, that pmake doesn't then detect changes to these directories dir.c: *An additional thing to consider is that pmake is used primarily dir.c: * (fish.c) and what pmake finds (./fish.c). job.c: *jobs. PMake is forked and a child shell created. main.c: *-f argument. Sets the .MAKEFLAGS PMake variable based on all the main.c: * on a different machine with pmake. make.c: * the start of the make. This is to keep pmake from getting make.c: *If the query flag was given to pmake, no job will be started, make.h: *The global definitions for pmake make.h:/* Attributes applied by PMake */ I thought our make *was* a hacked version of pmake ??? Makefile.dist even generates a 'pmake'. Michael -- Michael Elbel, PCS GmbH, Muenchen, Germany - me@FreeBSD.org Fermentation fault (coors dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0s3V0t-000Pa1C>