From: Bob Rossi <bob_rossi@cox.net>
To: gcc-help@gcc.gnu.org
Subject: mingw svn trunk failure
Date: Tue, 19 Dec 2006 15:54:00 -0000 [thread overview]
Message-ID: <20061219155354.GD32464@cox.net> (raw)
Hi,
Is this the correct place to talk about problems compiling gcc on mingw?
If I checkout svn trunk, and do,
mkdir gcc-builddir-1
cd gcc-builddir-1
../gcc/configure --disable-werror --with-gmp=/home/bobbybrasko/gcc/gmp/gmp \
--with-mpfr=/home/bobbybrasko/gcc/mpfr/prefixdir --host=mingw32 \
--target=mingw32 --prefix=/c/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
then I do,
cd gcc-builddir-1
make CFLAGS="-O2 -fomit-frame-pointer" \
CXXFLAGS="-mthreads -fno-omit-frame-pointer -O2" LDFLAGS=-s \
bootstrap 2>&1 | tee make-out.txt
Now, when I compile gcc, I get this error,
make[4]: Entering directory `/home/bobbybrasko/gcc/svn-head/gcc-builddir-1/gcc'
/home/bobbybrasko/gcc/svn-head/gcc-builddir-1/./gcc/xgcc -B/home/bobbybrasko/gcc/svn-head/gcc-builddir-1
/./gcc/ -L/home/bobbybrasko/gcc/svn-head/gcc-builddir-1/mingw32/winsup/mingw -L/home/bobbybrasko/gcc/svn
-head/gcc-builddir-1/mingw32/winsup/w32api/lib -isystem /home/bobbybrasko/gcc/svn-head/gcc/winsup/mingw/
include -isystem /home/bobbybrasko/gcc/svn-head/gcc/winsup/w32api/include -B/c/mingw/mingw32/bin/ -B/c/m
ingw/mingw32/lib/ -isystem /c/mingw/mingw32/include -isystem /c/mingw/mingw32/sys-include -O2 -I../../gc
c/gcc/../winsup/w32api/include -O2 -O2 -fomit-frame-pointer -DIN_GCC -W -Wall -Wwrite-strings -Wstri
ct-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -g -DHAVE_GTHR_DEFAULT -
DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../inclu
de -I../../gcc/gcc/../libcpp/include -I/home/bobbybrasko/gcc/gmp/gmp/include -I/home/bobbybrasko/gcc/mpf
r/prefixdir/include -I../../gcc/gcc/../libdecnumber -I../libdecnumber -DL_chkstk -xassembler-with-cpp -c
../../gcc/gcc/config/i386/cygwin.asm -o libgcc/./_chkstk.o
cc1.exe: internal compiler error: in add_standard_paths, at c-incpath.c:173
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[4]: *** [libgcc/./_chkstk.o] Error 1
make[4]: Leaving directory `/home/bobbybrasko/gcc/svn-head/gcc-builddir-1/gcc'
make[3]: *** [libgcc.a] Error 2
make[3]: Leaving directory `/home/bobbybrasko/gcc/svn-head/gcc-builddir-1/gcc'
make[2]: *** [all-stage1-gcc] Error 2
make[2]: Leaving directory `/home/bobbybrasko/gcc/svn-head/gcc-builddir-1'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/bobbybrasko/gcc/svn-head/gcc-builddir-1'
make: *** [bootstrap] Error 2
At c-incpath.c:173 I have,
/* If the compiler is relocated, and this is a configured
prefix relative path, then we use gcc_exec_prefix instead
of the configured prefix. */
gcc_assert (strncmp (p->fname, cpp_PREFIX,
cpp_PREFIX_len) == 0);
The values of the varaiables are,
p->fname=/c/mingw/include cpp_PREFIX=c:/mingw cpp_PREFIX_len=8
I've also tried with --prefix=/mingw, and that simply changes the fname
to /mingw/include, and it still fails at the same point. If I change the
prefix to C:/mingw, I get totally different errors. I don't think the
Makefile is happy with the : there.
Should I report this as a bug? Is there any easy way someone can help me
debug this further to fix it?
Thanks,
Bob Rossi
next reply other threads:[~2006-12-19 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 15:54 Bob Rossi [this message]
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
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=20061219155354.GD32464@cox.net \
--to=bob_rossi@cox.net \
--cc=gcc-help@gcc.gnu.org \
/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).