Date: Thu, 16 Nov 2000 23:39:49 -0500 Message-Id: <200011170439.XAA15862@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: djgpp-workers AT delorie DOT com In-reply-to: <5.0.1.4.0.20001116230739.00a55af0@pop5.banet.net> (pjfarley AT banet DOT net) Subject: Re: Help: Isn't libdbg the debugging version of libc? References: <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001116230739 DOT 00a55af0 AT pop5 DOT banet DOT net> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Can you point me at any info or docs on the right way to make and use a > debugging version of libc for gdb testing of fcntl? libdbg.a is a library of helper functions you need when building a debugger. It is not a version of libc.a built with -g. You'll need to check out the djgpp sources (http://www.delorie.com/djgpp/cvs.html) or unzip the djlsr*.zip archive, and build your own libc.a after altering the Makefiles to use -g instead of -O. > Secondary question: Why are we including libgcc.a in the LINK step in > "tests\makefile.inc"? Aren't we trying to test libc.a? What knowledge > am I missing here? libgcc.a is a support library needed by *anything* built with gcc.