From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16319 invoked by alias); 5 Dec 2007 15:17:16 -0000 Received: (qmail 16311 invoked by uid 22791); 5 Dec 2007 15:17:15 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Dec 2007 15:17:09 +0000 Received: from zps37.corp.google.com (zps37.corp.google.com [172.25.146.37]) by smtp-out.google.com with ESMTP id lB5FGsE7009785; Wed, 5 Dec 2007 15:16:54 GMT Received: from smtp.corp.google.com (spacemonkey1.corp.google.com [192.168.120.115]) by zps37.corp.google.com with ESMTP id lB5FGroa027990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Dec 2007 07:16:53 -0800 Received: from localhost.localdomain.google.com (69-36-227-130.cust.layer42.net [69.36.227.130] (may be forged)) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id lB5FGoDF002694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Dec 2007 07:16:52 -0800 To: Tom St Denis Cc: "gcc-help@gcc.gnu.org >> MSX to GCC" Subject: Re: Serious Bugs In Gcc Builds References: <4755A3B9.9060601@ix.netcom.com> <530296C8-E107-4676-A419-AC33415AB576@corp.earthlink.net> <4755AE18.8040801@ix.netcom.com> <47569920.2080500@ellipticsemi.com> From: Ian Lance Taylor Date: Wed, 05 Dec 2007 15:17:00 -0000 In-Reply-To: <47569920.2080500@ellipticsemi.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00122.txt.bz2 Tom St Denis writes: > Lionel B wrote: > > So it's a little tricky to build from source and install a large, > > complex, sophisticated, cross-platform, open source compiler > > suite. How surprising. Now... when did *anyone* - average user or > > not - build and install a MS compiler suite from source (apart from > > an MS employee)? > > > > I don't think it would be a radically huge task to get a decent > coverage of configurations [for both GCC and binutils] in some type of > wrapper script. Granted, you can't cover all possible weird > configurations, but why would something that can target the common > platforms [e.g. ARM, PPC, MIPS, x86] be so hard? This is free software. As the saying goes: patches welcome. Most of us are not going to write those scripts, because for simple cases we know the few steps required, and for complicated cases we use existing scripts like crosstool or buildroot. Ian