make 3.80 works, make 3.81 only works with SHELL=

2007-04-25 Thread Marty Leisner
Enclosed is the makefile from LPRng. I minimized it. It works on 3.80. On 3.81, it only works if you specify SHELL= on the command line... I've run this on a number of machines -- then I figured "try remake" and it worked -- then I realized remake was 3.80... There's a line SHELL="/bin/sh"

Manual isn't clear about where $(error) and $(warning) write to

2007-09-27 Thread Marty Leisner
I have 3.81.90 (cvs). Under "Functions That Control Make" It doesn't seem clear where $(warning) and $(error) get directed (stderr). $(info) is clear -- stdout. Instead of saying: "the resulting message is displayed" it would be more accurate to say "the resulting message is wri

Re: bug in cleaarcae mvfs for linux confuses make VPATH

2008-01-13 Thread Marty Leisner
You seem to be mixing up SDPParser.h and SDPContext.h -- but MVFS file system are not posix compatible -- I ran into this when I tried to diff two trees... You can just use snapshot views? (Or don't use clearcase ;-)) I suppose having a VPATH across two views will cause problems... Supposedly

debug -- displaying makefiles read...

2000-08-16 Thread Marty Leisner
I hacked up make several times to have an option to display makefiles read (which was recursive) -- similar to gcc -H. This was very, very useful -- especially understanding foreign systems with confusing make architectures. It should be easy to put in (I'll dig up my old patches). What should

should includes for make -n to actually make?

2002-01-29 Thread Marty Leisner
I'm running make 3.79.1 on linux... I normally do make -n to see what happens The makefile had: Makefile.dep: $(CXX) $(CXXFLAGS) -MM *.cc > Makefile.dep -include Makefile.dep and it seems the dep rule took higher priority then -n. I was under the impression -n would be non-destructiv

always echoing commands (patch)

2002-12-25 Thread Marty Leisner
was so easy, I should have done it much sooner!! (I've had this problem for more than a decade)!! The patch is wrt 3.80, attached below: Marty Leisner [EMAIL PROTECTED] --- make.h 2002/10/15 05:10:52 1.1 +++ make.h 2002/10/15 05:11:28 @@ -491,6 +491,7 @@ extern int env_over

Re: always echoing commands (patch)

2002-12-25 Thread Marty Leisner
When will it be integrated? I just got the cvs and it seemed it wasn't there... Its VERY useful... marty > If you look at but #111 in Savannah, you will find that someone already > reported this as a bug and supplied a patch to implement a new flag for > it. > > FYI. > > -- > ---

Re: --no-silent --no-quiet style option

2003-10-02 Thread Marty Leisner
"J. Grant" <[EMAIL PROTECTED]> writes on Wed, 24 Sep 2003 22:01:33 BST > Hello, > > on the 24/09/03 05:38, Paul D. Smith wrote: > > %% "J. Grant" <[EMAIL PROTECTED]> writes: > > > > jg> I think expanding the output would be helpful. I would like to > > jg>

Re: Schedule for GNU make 3.81

2005-02-16 Thread Marty Leisner
-- I find this very useful when debugging makefiles (as opposed to using strace). It shold be easy to fit this into --debug=h) Good to see a release... Marty Leisner ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/lis

automatic prerequisite problems

2005-11-10 Thread Marty Leisner
\.o[ :]*,\1.o $@ : ,g' < [EMAIL PROTECTED] > $@; \ rm -f [EMAIL PROTECTED] I've seen this annoying behavior for years...is there a better wah t handle this? Marty Leisner [EMAIL PROTECTED] ___ Bug-make mailing list Bug-make@gnu.org http

generating automatic prerequisites -- bug in doc

2005-12-16 Thread Marty Leisner
@@ @smallexample @group %.d: %.c -@set -e; rm -f $@@; \ +@@set -e; rm -f $@@; \ $(CC) -M $(CPPFLAGS) $< > $@@.; \ sed 's,\($*\)\.o[ :]*,\1.o $@@ : ,g' < $@@. > $@@; \ rm -f $@@. Marty Le

CURDIR for cur-dir in example in manual

2006-01-20 Thread Marty Leisner
Just looked at the most recent CVS copy of the manual on savannah... the technique for recursive makefiles of ifeq (0,[EMAIL PROTECTED]@}) cur-dir := $(shell pwd) is discussed, and passing pwd down with ${MAKE} cur-dir=${cur-dir}/$@ -C $@ all Isn't it a better idea to just use ${CURDI