[clug] Stupid make question... What commands/parameters get issued?

[steve jenkin]

I'm trying to understand where some problems in a build (conflicting
headers) are coming from, and it'd be really helpful to know exactly
what commands and parameters are being issued.

"make -d" (or --debug=...) print masses of detail, but is silent on what
commands are issued. (I get something like 'process started', 'finished'
when I use --debug=j. PID's don't equate to anything.).

"make -n" sort tells me what it *might* do, but in dynamic environments,
it can't be complete/correct.

"make -s" is the opposite of what I want :-)

Am I missing something??
I'd really like to think I am :-)

[On another note, how do you track down what gcc uses as its default
system includes??? I know I can set them with -isystem, -isysroot and
-idirisafter... But /usr/include and ???? are compiled in?]

-- 
Steve Jenkin, Info Tech, Systems and Design Specialist.
0412 786 915 (+61 412 786 915)
PO Box 48, Kippax ACT 2615, AUSTRALIA

sjenkin at canb.auug.org.au http://members.tip.net.au/~sjenkin