Date: Wed, 13 Aug 1997 17:10:02 -0700 (PDT) From: Steve Passe <smp@csn.net> To: freebsd-bugs Subject: Re: bin/4291: /usr/bin/make - inconsistent -j<n> flag parsing Message-ID: <199708140010.RAA09053@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/4291; it has been noted by GNATS. From: Steve Passe <smp@csn.net> To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: Subject: Re: bin/4291: /usr/bin/make - inconsistent -j<n> flag parsing Date: Wed, 13 Aug 1997 18:05:16 -0600 Hi, > >Number: 4291 > >Category: bin > >Synopsis: /usr/bin/make - inconsistent -j<n> flag parsing > >Description: > > /usr/bin/make can be used in two modes: with "parallel" > jobs (set with -j<n> flag) and in "compat mode" (-B flag). > > Currently "compat mode" is set by default (no -j nor -B > flags given) and if -B flag is given despite of presence/absence > of -j flag. > > BUT "compat mode" is also set without using -B flag > if -j<n> flag follows some "variable definition" on a command > line or in the MAKEFLAGS environment variable. > > >How-To-Repeat: > > 1) > make -j12 VAR=val all > > will work in "parallel mode", whereas > > make VAR=val -j12 all > > will set "compat mode". the supplied fix looks OK, but would this "fix" break any standard? Specifically, is there a standard we adhere to that says that all '-' options should preceed variable defines and other command line arguments? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708140010.RAA09053>