X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GDB on target w/o coprocessor
Date: 22 Jul 2004 16:01:36 GMT
Lines: 22
Message-ID: <2ma6n0FkuqsjU1@uni-berlin.de>
References: <pqRLc.37726$5D1 DOT 1638448 AT news4 DOT tin DOT it>
X-Trace: news.uni-berlin.de PdgF9nP4SX8wAafv7ploAQC8mSAt62UHdwgVq4TbZI4pUlyUy4xoLkEjE2
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

AndreA <andrea.galbusera <Ihatespammers>@teamware.it> wrote:

> This sounds reasonable... the target does not have a i387 chip.
> Since I had to compile my code with -lemu in order not to have the same
> problem,

That's not supposed to be necessary.  DJGPP has an automatic dynamic
load mechanism for an external 387 emulator.  You just have to install
it and possibly copy it into the program's build installation
directory.  See the FAQ for more.

> my question is: do I have to recompile gdb too? If so, is it ok to
> simply configure with --nfp option than make? 

If memory serves, there's a fundamental limitation that effectively
makes it impossible to use GDB on an FPU-less box.  You may have better
luck installing an FPU, or doing your debugging on "bigger" hardware.
Or even using GDB's remote debugging capabilities (if those still work).

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.