From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28565 invoked by alias); 13 May 2003 15:46:55 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 28503 invoked from network); 13 May 2003 15:46:54 -0000 Received: from unknown (HELO shell4.bayarea.net) (209.128.82.1) by sources.redhat.com with SMTP; 13 May 2003 15:46:54 -0000 Received: from eagercon.com (209-128-106-254.bayarea.net [209.128.106.254]) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4DFkjB01908; Tue, 13 May 2003 08:46:45 -0700 Message-ID: <3EC11365.7020707@eagercon.com> Date: Tue, 13 May 2003 15:46:00 -0000 From: Michael Eager User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Koning CC: rene.rebe@gmx.net, drow@mvista.com, gcc@gcc.gnu.org Subject: Re: building a gcc-3.3-prerelease cross-compiler References: <20030512.135453.424242140.rene.rebe@gmx.net> <20030512142238.GA13775@nevyn.them.org> <20030512.185423.115908471.rene.rebe@gmx.net> <16063.53985.772832.598267@pkoning.dev.equallogic.com> In-Reply-To: <16063.53985.772832.598267@pkoning.dev.equallogic.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg01317.txt.bz2 Paul Koning wrote: >>>>>>"Rene" == Rene Rebe writes: > > > Rene> Hi, On: Mon, 12 May 2003 10:22:38 -0400, Daniel Jacobowitz > Rene> wrote: > > Rene> [ ... error log ... ] > > >> > Any ideas? > >> > >> You can't build target libraries until after you've built glibc. > > Rene> Well nice that the cross-build instructions change between > Rene> every major release (and sometimes between minors ...). What > Rene> are the current instructions? > > Rene> (Is it intentional that the GCC install instructions point to > Rene> the rather old "Version: 1.01, Last Updated December 3, 1999" > Rene> CrossGCC/FAQ ? Maybe some more recent info should be included > Rene> in the install document ...) > > Indeed. It would be even better if they actually worked. I have > never seen ones that work. The closest I have come is procedures that > result in a build process that aborts at some point, but gets far > enough to produce a compiler that appears to function. I'm both sympathetic and frustrated by this as well. One consequence of not having documentation which is correct (or even close) is that we don't find bugs in the build process. It makes it difficult to tell whether a problem building a cross-compiler is (a) user error, (b) errors in the documentation, (c) unclear interactions between the configure options, (d) interactions or incompatibilities between components, or (e) errors in the implementation. I'd like to see the CrossGCC FAQ actually be a list of Questions and Answers, not a script for building a cross-compiler with one specific set of options for one particular purpose. IMO, we (the proverbial we, that is) could likely mine the GCC mailing list to find the common questions and the common answers. As Daniel said, lack of time/experience/motivation is a factor. I'm reluctant to say that I'll take a stab at a FAQ, given that I have limited time and every time I look at GCC configuration I feel that I'm being sucked into a tar pit. :-) -- Michael Eager Eager Consulting eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077