Re: Interpretation of "make -p"

[William_Morris JWA]

Hello 
Thanks for the reply.  But I am not really convinced.
For example, in the following:
 
        # Not a target:
        partab-test.d:
        #  A default or MAKEFILES makefile.
        #  Implicit rule search has been done.
        #  File does not exist.
        #  File has been updated.
        #  Failed to be updated.

The .d file is a dependency list being 'include'ed.
The 3rd line is a mystery.  The last two lines are 
contradictory.

Or in:

        # Not a target:
        partab-test: partab-test.o
        #  Command-line target.
        #  Implicit rule search has been done.
        #  Implicit/static pattern stem: `partab'
        ...

Why is partab-test both "not a target" and also the 
"Command-line target".

Or things like:
# Directories

        # /vobs/.../test/SCCS: could not be stat'd.
        # SCCS: could not be stat'd.
        # /vobs/.../test/../test/../srce//RCS: could not be stat'd.
        # /vobs/.../test (device 52429110, inode 195): 7 files, 
                20 impossibilities.
        # /vobs/.../test/../test (device 52429110, inode 195): 
                7 files, 20 impossibilities.
        # /vobs/.../test/../incl/RCS: could not be stat'd.

Ok SCCS and RCS directories don't exist, and there were 7 
files in the directory, but what are the impossibilities ?

Its these sorts of thing that always puzzle me whenever 
I try to work out why make is not doing what I expect.

Thanks again
--
William Morris


NB. GNU Make version 3.79.1, built for sparc-sun-solaris2.6