Message-Id: <5.0.1.4.0.20001117121723.03459060@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 17 Nov 2000 12:19:50 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Re: Help: Isn't libdbg the debugging version of libc?
In-Reply-To: <200011170439.XAA15862@envy.delorie.com>
References: <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001116230739 DOT 00a55af0 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001116230739 DOT 00a55af0 AT pop5 DOT banet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 11:39 PM 11/16/00 -0500, you wrote:
 >> 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.

Yes, I have the source zip already; that's what I am building 
with.  Thanks for the advice.

 >> 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.

OK, understood.  Thanks again for the info.

Back to work... :)
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)