compiling using gprof

i am trying to modifying my makefile so that I can use the gprof profiler. Hwowever the following file doesn,t generate the .o executable.

Code:

---


supersonic = Impinging_jet_21

OBJECTS = supersonic_ob.o flow_field.o matrix_col.o matrix_square.o matrix_functions.o matrix_derivative.o function_declarations.o output.o explicit.o Time_Step.o  Boundary.o

HEADERS = Constants.h flow_field.h function_declarations.h matrix_col.h 

ARCH = Linux
CPP = g++
CPPFLAGS = -D$(ARCH) -Wall -Wno-deprecated -pg
LIBRARIES = -lm -lg2c

supersonic: $(OBJECTS) $(HEADERS)
        $(CPP) $(CPPFLAGS) -o $(supersonic) $(OBJECTS) $(LIBRARIES)

clean:
        rm *.o $(supersonic)

.c.o:
        gcc  -Wall -pg $<

---

Code:

---

.c.o:

---

This rule is for creating a file called ".c.o" from nothing. It's not a valid pattern rule.

Quote:

---

Originally Posted by CornedBee

Code:

---

.c.o:

---

This rule is for creating a file called ".c.o" from nothing. It's not a valid pattern rule.

---

Are you sure about this? I thought it was a valid Makefile rule for creating .o files from .c files.

Cheers,
Sander

--
Computer Programming: An Introduction for the Scientifically inclined

I'm fairly sure, yes.

There's other things wrong with the Makefile, too, such as passing the CPPFLAGS only to linking, but not to what you thought was compiling.

You shouldn't even need the pattern rule. It's built in. Just set the CFLAGS correctly. Set LD to g++ to get C++ linking.

Quote:

---

Originally Posted by CornedBee

I'm fairly sure, yes.

There's other things wrong with the Makefile, too, such as passing the CPPFLAGS only to linking, but not to what you thought was compiling.

You shouldn't even need the pattern rule. It's built in. Just set the CFLAGS correctly. Set LD to g++ to get C++ linking.

---

I took the liberty of looking it up:

Suffix Rules

Also here:

Managing Projects with GNU Make, Third Edition (look on page 24). The book does state: "Suffix rules were make’s original means for writing general rules. GNU make includes support for suffix rules, but they are considered obsolete having been replaced by pattern rules that are clearer and more general."

I agree with your remarks on what's broken with the Makefile, though.

--
Computer Programming: An Introduction for the Scientifically Inclined

don't you need a intruction

Code:

---

.SUFIXXES: .o .c

---

to tell make to look out for .c and .o files ?

as to

Code:

---

.c.o

---

im 110% sure its a suffixe rule that "teachs" make how to create a .o file from a .c
but you're instruction is not creating a .o file since i think you forgot the -c flag in

Code:

---

.c.o:
        gcc  -Wall -pg $<

---

should be

Code:

---

.c.o:
        gcc  -Wall -c -pg $<

---