From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14755 invoked by alias); 19 Dec 2007 12:36:38 -0000 Received: (qmail 14745 invoked by uid 22791); 19 Dec 2007 12:36:37 -0000 X-Spam-Check-By: sourceware.org Received: from exprod6og104.obsmtp.com (HELO psmtp.com) (64.18.1.187) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Dec 2007 12:36:28 +0000 Received: from source ([192.150.11.134]) by exprod6ob104.postini.com ([64.18.5.12]) with SMTP; Wed, 19 Dec 2007 04:36:24 PST Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id lBJCY4in012935; Wed, 19 Dec 2007 04:34:04 -0800 (PST) Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id lBJCaJRC022436; Wed, 19 Dec 2007 04:36:19 -0800 (PST) Received: from namailgen.corp.adobe.com ([10.8.192.91]) by fe2.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Dec 2007 04:36:19 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Problem building gcc-4.2.2 on 64-bit ubuntu linux Date: Wed, 19 Dec 2007 12:36:00 -0000 Message-ID: References: <4768E104.2000801@cadenas.de> From: "John (Eljay) Love-Jensen" To: "Thomas Mittelstaedt" , 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/msg00339.txt.bz2 Hi Thomas, >../configure --prefix=3D/opt/gcc-4.2.2 --enable-version-specific-runtime-libs --enable-static --enable-shared --enable-languages=3Dc,c++,java,objc,obj-c++ --enable-threads=3Dposix --enable-nls --enable-__cxa_atexit --enable-libstdcxx-debug --enable-checking=3Drelease x86_64-linux-gnu It appears that you are attempting to build GCC from within a subdirectory = of the GCC source code (instead of, say, a peer directory to the GCC source= code). Since that situation is not supported as per , do you get the same problem if you build to a peer directory= to the source code? Note: the source code tree may be "tainted" and could need to be "rm -rf" = and "tar -x" afresh. I do not know if this is related to the problem encountered or not. Just o= ne of the variables to consider taking out of the equation. Sincerely, --Eljay