X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
From:	Eli Zaretskii <eliz AT gnu DOT org>
To:	Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
CC:	djgpp AT delorie DOT com
In-reply-to:	<201101190016.02772.juan.guerrero@gmx.de> (message from Juan
	Manuel Guerrero on Wed, 19 Jan 2011 00:16:01 +0100)
Subject:	Re: Difficulries with GDB 7.2 compiled with DJGPP
References:	<201101152018 DOT 51379 DOT juan DOT guerrero AT gmx DOT de> <E1PeGAp-00021L-98 AT fencepost DOT gnu DOT org> <201101190016 DOT 02772 DOT juan DOT guerrero AT gmx DOT de>
Message-Id:	<E1PfZPj-0005DP-0P@fencepost.gnu.org>
Date:	Wed, 19 Jan 2011 09:53:35 -0500
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
> Date: Wed, 19 Jan 2011 00:16:01 +0100
> 
> The reason why the GDB produced with DJGPP 2.04 is brocken is that the go32-nat.o
> and i386-nat.o files are not compiled.  This is because go32.mh snippet is not
> included to the gdb/Makefile by the configure script.  The script checks for
> host system/build system = i786-pc-msdosdjgpp and for target system = i586-pc-msdosdjgpp
> As can be seen target and host system does not match and the configure scripts
> decides to build a cross debugger or something else.
> The reason is that config.sub has the i586-pc-msdosdjgpp value hardcoded and
> this does not match the value returned by config.sub.

Thanks for investigating this snafu.

How come the v2.03 build avoided this issue?

- Raw text -