X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com From: Eli Zaretskii To: Juan Manuel Guerrero CC: djgpp AT delorie DOT com In-reply-to: <201101191925.46252.juan.guerrero@gmx.de> (message from Juan Manuel Guerrero on Wed, 19 Jan 2011 19:25:46 +0100) Subject: Re: Difficulries with GDB 7.2 compiled with DJGPP References: <201101152018 DOT 51379 DOT juan DOT guerrero AT gmx DOT de> <201101190016 DOT 02772 DOT juan DOT guerrero AT gmx DOT de> <201101191925 DOT 46252 DOT juan DOT guerrero AT gmx DOT de> Message-Id: Date: Wed, 19 Jan 2011 19:03:15 -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 Precedence: bulk > From: Juan Manuel Guerrero > Date: Wed, 19 Jan 2011 19:25:46 +0100 > Cc: djgpp AT delorie DOT com > > > How come the v2.03 build avoided this issue? > > > config.sub produces for an input string that contains "djgpp" the hardcoded > output string "i586-pc-msdosdjgpp". config.guess uses uname to detect the > processer type. This script concatenates the output produced by "uname -m" > together with the string "pc-msdosdjgpp". The 2.04 version of uname returns > "i786" but the 2.03 version of uname returns "i586". In those cases we get for > the 2.04 version: i786-pc-msdosdjgpp and for > the 2.03 version: i586-pc-msdosdjgpp. Can you suggest a change in config.sub that would accommodate both v2.03 and v2.04? If so, please submit that change to config.sub maintainers. Thanks.