Re^2: dmake warning question

in reply to Re: dmake warning question
in thread dmake warning question

Thanks! (I think :) ) the first link says I can make the warning go away:

508:    #i64572# Make dmake warn if the time stamp of a target is not 
+updated
509-    after making the target. This warning can be silenced using th
+e
510-    .SILENT attribute.
544-    * make.c:
[download]

The second link might well explain what is going on if I read it a few more times. I will put it somewhere in my todo stack--- middle-ish I think. When it says to use the .SILENT attribute do you (or anyone watching) know the syntax?

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."

Comment on Re^2: dmake warning question Download Code

Replies are listed 'Best First'.
Re^3: dmake warning question by roboticus (Chancellor) on Jan 07, 2011 at 09:42 UTC
According to the dmake manual found here: http://lmgtfy.com, you can: put "-s" on the command line, put the line ".SILENT : blibdirs pure_all" in your Makefile, modify your Makefile and put ".SILENT" after the target name in the definition, like: `mylib.a .LIBRARY : mem1.o mem2.o mem3.o` It will likely support other methods, too, as I only briefly glanced at the documentation. ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply] [d/l]
Re^3: dmake warning question by CountZero (Bishop) on Jan 07, 2011 at 16:37 UTC
It makes the warnings go away (or rather remain silent), but doesn't that mean that you will not be informed of other warnings too? It seems a bit like to comment-out "`use strict; use warnings;`" to get rid of those "superfluous" Global symbol "$..." requires explicit package name at ... messages, until you make a real typo and the program blows up and another bank keels over. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply] [d/l]

In Section Seekers of Perl Wisdom