From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29199 invoked by alias); 19 Sep 2006 05:37:26 -0000 Received: (qmail 29190 invoked by uid 22791); 19 Sep 2006 05:37:25 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 19 Sep 2006 05:37:21 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 7119C48CBE4; Tue, 19 Sep 2006 01:37:19 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20929-01-10; Tue, 19 Sep 2006 01:37:19 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id E17C448CF7E; Tue, 19 Sep 2006 01:37:18 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id BB5A847F00; Mon, 18 Sep 2006 22:37:17 -0700 (PDT) Date: Tue, 19 Sep 2006 05:37:00 -0000 From: Joel Brobecker To: Ray Duran Cc: gdb@sourceware.org Subject: Re: gdb build error Message-ID: <20060919053717.GT26334@adacore.com> References: <3CE39F664D1EE14293F6923CD00E42C704CD96A5@montremsg32.na.future.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CE39F664D1EE14293F6923CD00E42C704CD96A5@montremsg32.na.future.ca> User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00099.txt.bz2 Ray, (sorry about the delay - work suddenly became crazy) > -Yes, I agree that the file probably existed. > > - I am not sure what mirror site I downloaded the file from, but the > name of > the tar is: insight-6.5.tar.bz2. Have you been able to build GDB since then? > - I followed the list of configure and build command that I found on > the eCos page for installing GNU tools. My final application is to use > eCos on an ARM. That may be where you got the sources from. I don't know what this package contains, so it's going to be difficult for me to help you further. Maybe the people who actually created the tarball might be able to help you further. Otherwise, check before doing the configure that this file exists. Then do the configure, and check again. Then do the build, and check again. If it disappears during the build as I suspect, then grep for that filename in the build output - that should give you a good clue as to what is happening. As a workaround, you may want to retrieve that file and copy it back right after the build failed, and then restart the build. That should work. Another approach, of course, is to install flex, check out www.gnu.org. -- Joel