From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6960 invoked by alias); 1 Dec 2007 02:14:18 -0000 Received: (qmail 6948 invoked by uid 22791); 1 Dec 2007 02:14:17 -0000 X-Spam-Check-By: sourceware.org Received: from secure.latencyzero.com (HELO mail.latencyzero.com) (64.71.153.217) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 01 Dec 2007 02:14:07 +0000 Received: (qmail 13260 invoked from network); 1 Dec 2007 02:14:06 -0000 Received: from unknown (HELO rmann1.internal.xbow.com) (rmann@63.64.55.212) by 0 with ESMTPA; 1 Dec 2007 02:14:06 -0000 Message-Id: <8BD833AA-8B16-4B4E-B9E7-49D6670E68C4@latencyzero.com> From: Rick Mann To: gcc-help@gcc.gnu.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Need help building combined gcc/binutils/newlib Date: Sat, 01 Dec 2007 02:14:00 -0000 X-Mailer: Apple Mail (2.915) 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/msg00001.txt.bz2 I've looked at several archive messages, and many OLD instructions, and I still can't quite figure out how to do a combined build of GCC targeting xscale-elf. I need to do this from release tars. I downloaded gcc-4.2.1, binutils-2.18, and newlib-1.15. I extract these all into one dir: gccbuild/ binutils-1.15/ gcc-4.2.1/ newlib-1.15/ Then I wasn't sure how to use the symlink-tree script, so I tried this: cd gccbuild mkdir src cd src ../binutils-2.18/symlink-tree ../binutils-2.18 ../binutils-2.18/symlink-tree ../newlib-1.15 ../binutils-2.18/symlink-tree ../gcc-4.2.1 Then cd .. mkdir build cd build ../src/configure --prefix=/usr/local/gcctest \ --target=xscale-elf \ --enable-languages=c,c++ \ --with-newlib --disable-nls \ --disable-libssp --with-float=soft It did a short configure, then I tried "make all". It ran for a while, then got into a seemingly endless series of messages like this: > Fatal configuration error. See the libtool docs for more information. > : ltconfig version `' does not match ltmain.sh version `1.4a-GCC3.0' I suspect part of my problem is the order in which I'm running symlink- tree. But I could just be way off target. Can someone please explain to me the process (or point me to a resource that does)? Thank you very much! -- Rick