From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15730 invoked by alias); 25 Sep 2006 19:08:12 -0000 Received: (qmail 15706 invoked by uid 22791); 25 Sep 2006 19:08:11 -0000 X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 25 Sep 2006 19:08:07 +0000 Received: from home.wh0rd.org (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 6760C64963 for ; Mon, 25 Sep 2006 19:08:02 +0000 (UTC) Received: (qmail 1590 invoked from network); 25 Sep 2006 15:07:15 -0400 Received: from unknown (HELO vapier) (192.168.0.2) by 192.168.0.1 with SMTP; 25 Sep 2006 15:07:15 -0400 From: Mike Frysinger To: Michael Snyder Subject: Re: [patch ping] change linux-gnu* -> linux* in libtool files Date: Mon, 25 Sep 2006 19:08:00 -0000 User-Agent: KMail/1.9.4 Cc: Ian Lance Taylor , binutils@sourceware.org, gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org References: <200609241801.43629.vapier@gentoo.org> <200609251359.17234.vapier@gentoo.org> <1159210072.24808.23.camel@localhost.localdomain> In-Reply-To: <1159210072.24808.23.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7789294.xDTHiPWE1s"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609251508.00560.vapier@gentoo.org> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00170.txt.bz2 --nextPart7789294.xDTHiPWE1s Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-length: 754 On Monday 25 September 2006 14:47, Michael Snyder wrote: > Not to say you're wrong, but this is the first I've heard > that linux-gnu implies glibc. Is there someplace where this > is written? common practice ? :) in the uClibc world we use $arch-$vendor-linux-uclibc to keep things clean = and=20 sep from the host glibc toolchain $arch-$vendor-linux-gnu ... when we=20 proposed adding support for *-linux-uclibc and *-linux-newlib and=20 *-linux-dietlibc to binutils, the cleaner solution was to simply accept=20 *-linux-* in configure files upstream libtool changed their files a while ago to accept 'linux*)' rather= =20 than 'linux-gnu*)' ... so my patch isnt treading into new territory, it's=20 backporting updates from upstream libtool -mike --nextPart7789294.xDTHiPWE1s Content-Type: application/pgp-signature Content-length: 827 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iQIVAwUARRgpEEFjO5/oN/WBAQKE6Q/+IMFpRB4Ub+4IMEWEab9+oCSDAXp1asAT sBNpDAZaghhFH9kUdn1hTiQp9b/5ezS8xx86oRXc6djiPUPWIL16+EVJG7m3jLp/ ceqqUSfKPKAO8ZDgw2Fn9vWGV4pnWtoCCxpC12PIYrQ9ZW7tRgyHkUVg1sJtfq6v mtcz+Ti3eJngFZzJJpoVIsbiFLJRfvysYRA1Zrx7rJgtmcpch+WLRw7/A41iYqUh Oquj5n924TR4GfxLcEMsPknbgrm4yT9Yt56p0Lkn9qgaD7ieaL1m82xlKVavaHJ+ g9IN4qccjYia5L4UiaQhlpqxAsP3YkcwQ4iEI+nS31oLnqcrJsuOGP7SB9mwR3m+ IwN3YvMhCFcW3WLI9b7Q1NOfMhl4i+bZ8kV9jMSzVBDu5Ml6FTXDUUj6hCQO00w1 svhW0p0sUD/2tqU3QsHSSTw5dvig+xX83RINZmN5oU9UbvCv6HFmom5yfJEW6CJ2 8GMR3iR4mvb2Caw/EAJrDxWC+DwegJcsj+Z2K5Cij7SPO3hhNTjlkTHVjKQH+3VS lMiYkdMj35h+foOd9Rffkj2w24tYR4yr3nwNH/EH3hvzk3Krw/c/NiEYFsvpWrc3 iSVy2zECV+i1IM3NcE7J3kW2hABvDfNyA4Qnr5hAZlZ6uSPoXKtC3fzaVEOsI9Xy yX2TG53imS8= =HApH -----END PGP SIGNATURE----- --nextPart7789294.xDTHiPWE1s--