Thread: gcc error: undefined reference

So I am attempting to clean up my makefile and have run into an issue.

I am receiving the errors:

parser.c:18: undefined reference to `parser1'
parser.c:20: undefined reference to `parser2'

And this is my makefile:

Code:

CC=gcc
CFLAGS=-std=c99 -g3 -Wall

parser: parser.o parsers.a
    $(CC) $(CFLAGS) -o parser parser.o parsers.a

parser.o: parser.c parser.h
    $(CC) $(CFLAGS) -c parser.c

parsers.a: parser1.a parser2.a parse_misc.o
    ar cr parsers.a parser1.a parser2.a parse_misc.o

parser1.a: parser1.c parser1.h constants.h packet1.o
    $(CC) $(CFLAGS) -c parser1.c
    ar cr parser1.a parser1.o packet1.o

parser2.a: parser2.c parser2.h constants.h packet2.o
    $(CC) $(CFLAGS) -c parser2.c
    ar cr parser2.a parser2.o packet2.o

packet1.o: packet1.c packet1.h constants.h
    $(CC) $(CFLAGS) -c packet1.c


packet2.o: packet2.c packet2.h constants.h
    $(CC) $(CFLAGS) -c packet2.c

parse_misc.o: parse_misc.c parse_misc.h
    $(CC) $(CFLAGS) -c parse_misc.c

clean:
    rm -f *.o *.a *~ parser

I have an old makefile that works just fine so I know the problem is not with missing '#include's or some other code related problem, it is a problem with my makefile.

An alternate option that I choose to do is to compile my source codes manually. A makefile should automate many of the compiling for you. However it could get too complex so "keep it simple silly" is what I hear.

Originally Posted by Tien Nguyen

An alternate option that I choose to do is to compile my source codes manually. A makefile should automate many of the compiling for you. However it could get too complex so "keep it simple silly" is what I hear.

You are completely useless. All you are doing is wasting people's time. Is that what jesus would do? Your code is so terrible and your jesus-crap was so idiotic that I think you're just a troll. Added to ignore list.

jdodle's problem is presumably related to creating a nested archive, an archive of archives. He should either create a "thin" archive (if that fits his needs, but this does not actually add the object code itself to the archive but instead references the original object files) or extract the files and add the object files themselves to the final archive (or just add the original object files since they are presumably still around).

Originally Posted by algorism

You are completely useless. All you are doing is wasting people's time. Is that what jesus would do? Your code is so terrible and your jesus-crap was so idiotic that I think you're just a troll. Added to ignore list.

A little over the top... but thanks for putting a troll in its place.

To be honest I'm not doing any archiving, I simply wanted to reduce the number of characters per line to avoid text wrapping and improve readability. I think this is the best way to do it, though if anyone has a better suggestion I'm all ears. The way I had it originally, each object file had its own target but then the executable was this massive multiline dependency list and a linking list that was just as long. I will probably reduce the number of targets I have but I wanted to start out fairly verbose to try and make bugs in the Makefile more transparent. The reason I'm creating libraries is to join multiple object files into one file, I couldn't find any other way to do that. Other than that... I would say it is actually pretty simple for having 13 source/header files.

Originally Posted by Salem

First, use the 'nm' utility to find out what symbols are actually defined.

Great tool tip, this is awesome.

Originally Posted by Salem

Second, your naming of libraries is suspect.

Works great after switching to linker flags and proper naming conventions. I had originally done it this way but I now realize I forgot to start the name with 'lib' so I thought I would just name them directly without using flags; obviously that didn't work. Thanks!