From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13048 invoked by alias); 18 Oct 2006 13:27:53 -0000 Received: (qmail 12991 invoked by uid 22791); 18 Oct 2006 13:27:51 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao03.cox.net (HELO eastrmmtao03.cox.net) (68.230.240.36) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Oct 2006 13:27:46 +0000 Received: from eastrmwml04.mgt.cox.net ([172.18.52.69]) by eastrmmtao03.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20061018132745.QBHT23863.eastrmmtao03.cox.net@eastrmwml04.mgt.cox.net>; Wed, 18 Oct 2006 09:27:45 -0400 Message-ID: <21051253.1161178065993.JavaMail.root@eastrmwml04.mgt.cox.net> Date: Wed, 18 Oct 2006 13:38:00 -0000 From: To: gcc@gcc.gnu.org Subject: Re: build error Cc: Brian Dessent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sensitivity: Normal X-IsSubscribed: yes 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 X-SW-Source: 2006-10/txt/msg00399.txt.bz2 ---- Brian Dessent wrote: > > Consider posting this kind of question to gcc-help@ instead. OK, I will. > bob_rossi@cox.net wrote: > > > I just ran these commands: > > > > svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc > > mkdir builddir > > cd builddir > > CFLAGS="-g" ../gcc/configure --enable-languages=c,c++ --enable-checking \ > > --disable-bootstrap --prefix=$PWD/../prefixdir > > make -s > > make install > > > > and I got the attached compile error. Is this a known issue on an > > Althlon64 processor? Are there any work arounds? > > I don't think it has anything to do with your processor, but the fact > that your build directory is a subdirectory of the source tree is > generally a no-no. See . > > Brian No, the build directory is not inside the source directory. The svn command checks out a gcc/ directory. Then I make a builddir/ directory at the same level as the gcc/ directory. I tend to agree it's not a processor problem though. I had this exact configuration working on my ubunut box last week. My machine died, so I'm using a friend's gentoo box. This is the error I'm seeing now. Thanks, Bob Rossi