From:	kagel AT quasar DOT bloomberg DOT com
Date:	Wed, 25 Sep 1996 08:26:12 -0400
Message-Id:	<9609251226.AA15148@quasar.bloomberg.com >
To:	cs3prj04 AT lion DOT cs DOT latrobe DOT edu DOT au
Cc:	djgpp AT delorie DOT com
In-Reply-To:	<525dvj$n79@lion.cs.latrobe.edu.au> (cs3prj04@lion.cs.latrobe.edu.au)
Subject:	Re: g++ linke error.
Reply-To:	kagel AT dg1 DOT bloomberg DOT com

   Errors-To: postmaster AT ns1
   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
   Date: 23 Sep 1996 07:24:35 GMT
   Organization: Comp.Sci & Comp.Eng, La Trobe Uni, Australia
   Lines: 16
   Distribution: world
   Nntp-Posting-Host: lion.cs.latrobe.edu.au
   Dj-Gateway: from newsgroup comp.os.msdos.djgpp
   Content-Type: text
   Content-Length: 653

   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.

If you post a sample of the messages you do not understand someone will surely
explain them to you.  

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats

- Raw text -