From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28935 invoked by alias); 20 Dec 2006 00:29:29 -0000 Received: (qmail 28926 invoked by uid 22791); 20 Dec 2006 00:29:28 -0000 X-Spam-Check-By: sourceware.org Received: from centrmmtao02.cox.net (HELO centrmmtao02.cox.net) (70.168.83.82) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 20 Dec 2006 00:29:20 +0000 Received: from eastrmimpo02.cox.net ([68.1.16.120]) by centrmmtao02.cox.net (InterMail vM.6.01.06.03 201-2131-130-104-20060516) with ESMTP id <20061220002918.VZDK25837.centrmmtao02.cox.net@eastrmimpo02.cox.net>; Tue, 19 Dec 2006 19:29:18 -0500 Received: from black ([70.181.32.198]) by eastrmimpo02.cox.net with bizsmtp id 0oU51W00B4GV2Jm0000000; Tue, 19 Dec 2006 19:28:05 -0500 Received: from bob by black with local (Exim 4.62) (envelope-from ) id 1GwpKf-0002Mk-RM; Tue, 19 Dec 2006 19:29:17 -0500 Date: Wed, 20 Dec 2006 00:29:00 -0000 From: Bob Rossi To: gcc-help@gcc.gnu.org, carlos@codesourcery.com, mark@codesourcery.com Subject: Re: mingw svn trunk failure Message-ID: <20061220002917.GE3022@cox.net> Mail-Followup-To: gcc-help@gcc.gnu.org, carlos@codesourcery.com, mark@codesourcery.com References: <20061219155354.GD32464@cox.net> <20061219223224.GA3022@cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061219223224.GA3022@cox.net> User-Agent: Mutt/1.5.12-2006-07-14 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: 2006-12/txt/msg00287.txt.bz2 O Tue, Dec 19, 2006 at 05:32:24PM -0500, Bob Rossi wrote: > On Tue, Dec 19, 2006 at 10:53:54AM -0500, Bob Rossi wrote: > > Hi, > > > > Is this the correct place to talk about problems compiling gcc on mingw? > > > > If I checkout svn trunk, and do, > > I've reverted this patch, > http://gcc.gnu.org/viewcvs?view=rev&revision=119017 > and I am able to build svn trunk without a problem. It may not solve the > problem I'm having (making gcc relocatable), but it does build. > > Mark or Carlos, do you have any idea why this patch is giving me an > assertion? What should I do? Hi Carlos, I'm sorry. I've run it 2 ways. With prefix=/c/mingw and with prefix=/mingw. prefix=/mingw is the historically correct way to do this from what I understand. I only tried it with /c/mingw once as a test to see if it would work around the problem I found. With --prefix=/mingw my configure line was, mkdir gcc-builddir-0 cd gcc-builddir-0 ../gcc/configure \ --disable-werror \ --with-gmp=/home/bobbybrasko/gcc/gmp/gmp \ --with-mpfr=/home/bobbybrasko/gcc/mpfr/prefixdir \ --host=mingw32 \ --target=mingw32 \ --prefix=/mingw \ --program-suffix="-4.1" \ --with-gcc \ --with-gnu-ld \ --with-gnu-as \ --enable-threads=win32 \ --disable-nls \ --enable-languages=c,c++ \ --disable-win32-registry \ --disable-shared \ --enable-static \ --without-x \ --enable-libstdcxx-debug \ 2>&1 | tee configure-out.txt Here was the build line, cd gcc-builddir-0 make \ CFLAGS="-O2 -fomit-frame-pointer" \ CXXFLAGS="-mthreads -fno-omit-frame-pointer -O2" \ LDFLAGS=-s \ bootstrap 2>&1 | tee make-out.txt And the debug info was found here, http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01356.html p->fname=/mingw/include cpp_PREFIX=C:/mingw cpp_PREFIX_len=8 Sorry about the confusion. Thanks, Bob Rossi