From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12152 invoked by alias); 18 Jun 2002 23:56:21 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 12111 invoked from network); 18 Jun 2002 23:56:19 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sources.redhat.com with SMTP; 18 Jun 2002 23:56:19 -0000 Received: (qmail 12485 invoked by uid 20157); 18 Jun 2002 23:56:18 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Jun 2002 23:56:18 -0000 Date: Tue, 18 Jun 2002 16:56:00 -0000 From: Hans-Peter Nilsson X-Sender: To: Mark Butcher cc: gcc , gcc-help Subject: Re: Tutorial 3 In-Reply-To: <200206181740_MC3-1-2E1-A114@compuserve.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-06/txt/msg00172.txt.bz2 On Tue, 18 Jun 2002, Mark Butcher wrote: > I think that Bill Gatliff's site should be compulsory reading for anyone > contemplating a GCC cross-build. [www.billgatliff.com]. Although there is > only a relatively small amount of information, it is the information that > is needed and the example script is even more or less understandable to a > dummy like myself. > > Build BINUTILS > Build a minimum gcc without headers and libraries > Build NEWLIB with the minimum gcc > Build the full GCC Or build them all at once, with a unified tree. Try : add "make install", but strip dejagnu and gdb parts to taste. Alternatively, using tarballs with gcc, binutils and newlib instead of CVS, with releases reasonably in phase, just untar them into the same directory, then configure --target=..., make and make install. The simulator targets (most of them) are actually bare-bones *-elf cross-toolchains; the simulator is an add-on from the gdb package. Neccessary I/O libraries are built as part of the newlib/libgloss package. It's not rocket science. brgds, H-P PS. Houston..? Houston..? ...darn, not again.