From mint-bounce@lists.fishpool.fi Tue Jan 22 17:33:53 2008 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <478B548A.4000007@freesbee.fr> Date: Mon, 14 Jan 2008 13:24:42 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: mint Subject: Re: [MiNT] gcc 4.2.2 patch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-OriginalArrivalTime: 14 Jan 2008 12:23:56.0253 (UTC) FILETIME=[551D30D0:01C856A8] X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freemint id m0MGP1ed004618 Status: X-Status: X-Keywords: Andreas Schwab a écrit : >> atarist[e]:*MiNT:*:* | atarist[e]:*mint:*:* | atarist[e]:*TOS:*:*) >> - echo m68k-atari-mint${UNAME_RELEASE} >> + echo m68k-atari-mint > > If you want a different name just specify it explicitly via > --build/--host/--target. There is nothing wrong with putting the > release in the canonical name. Of course, it is possible to build the tools with --build=m68k-atari-mint. However, the job of config.guess is to guess the correct host triplet in order to automatically use it. Linux uses i486-linux-gnu (on my Debian system) Cygwin uses i686-pc-cygwin MiNT usually use m68k-atari-mint for the cross-tools I can hardly understand why something like m68k-atari-mint1.16 could be usefull. Maybe if the different versions of the kernel would be completely incompatible ? As far as I know, it is not the case. Thus, it seems to me that the patch proposed by MiKRO is a good thing. However, the trailing ${UNAME_RELEASE} may have been put there intentionally. In that case, whe have to discover why. Note that this stuff has been in the official config.guess of GCC since Sat May 22 05:17:55 1999. See the log here: http://gcc.gnu.org/viewcvs/branches/gcc-4_2-branch/config.guess?view=log -- Vincent Rivière