From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3FD9436F.2060206@kegel.com>
Date: Thu, 11 Dec 2003 20:26:23 -0800
From: Dan Kegel <dank@kegel.com>
MIME-Version: 1.0
To: Beena <beena@gdatech.com>
Cc: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>,
	"'Ashwin Bihari'" <raz0redge@hotmail.com>, listmember@orkun.us,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross-compile package combinations
References: <FFELLIHDBBOAPGLCBDIPEEADCDAA.beena@gdatech.com>
In-Reply-To: <FFELLIHDBBOAPGLCBDIPEEADCDAA.beena@gdatech.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Sender: owner-linuxppc-embedded@lists.linuxppc.org
List-Id: <linuxppc-embedded@lists.linuxppc.org>


Beena wrote:
> I have observed the same errors when trying to build the bootstrap gcc
> 3.2.3. I understand that
> this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
> files. So I first built gcc 2.95.3,
> then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
> 3.2.3) and it compiled fine.

One of the reasons I did crosstool was to avoid that kind of
hackery.  With crosstool, you don't need to build gcc 2.95.3
just to build gcc 3.2.3.  Crosstool does clean builds from pristine,
minimally patched source.
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/