Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

Re: dmake warning question

by Anonymous Monk
on Jan 07, 2011 at 00:23 UTC ( [id://880973]=note: print w/replies, xml ) Need Help??


in reply to dmake warning question

Replies are listed 'Best First'.
Re^2: dmake warning question
by hsmyers (Canon) on Jan 07, 2011 at 05:08 UTC
    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:
    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."

      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.

      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

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://880973]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (5)
As of 2024-03-19 08:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found