From:	cs3prj04 AT lion DOT cs DOT latrobe DOT edu DOT au (Cs3prj Group 04)
Newsgroups:	comp.lang.c,comp.lang.c++,comp.os.msdos.djgpp
Subject:	g++ linke error.
Date:	23 Sep 1996 07:24:35 GMT
Organization:	Comp.Sci & Comp.Eng, La Trobe Uni, Australia
Lines:	16
Distribution:	world
Message-ID:	<525dvj$n79@lion.cs.latrobe.edu.au>
NNTP-Posting-Host:	lion.cs.latrobe.edu.au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I am reasonably good at finding and solving logical errors in C 
programs but when it comes to link errors I constantly find myself
floundering.

I find the error output of c linkers to be absolute meaningless waffle.

I recently got an undefined symbol error in a source file of around 4000
lines. As per usual there is no source file line number specified nor
even a function name to go on.

I was there fore forced to comment out the contents of every function and
uncomment them one by one, re-compiling each time, until the error 
re-appeared.

Surely there is a better way. I have tried nm but I find the output of that
to be equally meaningless.

- Raw text -