From: Bob Rossi <bob_rossi@cox.net>
To: gcc-help@gcc.gnu.org, carlos@codesourcery.com, mark@codesourcery.com
Subject: Re: mingw svn trunk failure
Date: Wed, 20 Dec 2006 00:29:00 -0000 [thread overview]
Message-ID: <20061220002917.GE3022@cox.net> (raw)
In-Reply-To: <20061219223224.GA3022@cox.net>
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
next prev parent reply other threads:[~2006-12-20 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 15:54 Bob Rossi
2006-12-19 22:32 ` Bob Rossi
2006-12-19 22:50 ` Carlos O'Donell
2006-12-19 22:59 ` Bob Rossi
2006-12-19 23:58 ` Carlos O'Donell
2006-12-20 0:24 ` Bob Rossi
2006-12-20 1:23 ` Carlos O'Donell
2006-12-20 1:56 ` Bob Rossi
2006-12-20 2:33 ` Carlos O'Donell
2006-12-19 23:47 ` Carlos O'Donell
2006-12-20 0:29 ` Bob Rossi [this message]
2006-12-20 1:45 ` Carlos O'Donell
2006-12-20 4:53 ` Bob Rossi
2006-12-20 17:24 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061220002917.GE3022@cox.net \
--to=bob_rossi@cox.net \
--cc=carlos@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mark@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).