public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Henningsen <kai@qualify.domain.khms.westfalen.de>
To: gcc@gcc.gnu.org
Cc: Kai Henningsen <kai@qualify.recipient.khms.westfalen.de>
Subject: mainline bootstrap failure
Date: Thu, 23 Jan 2003 19:59:00 -0000	[thread overview]
Message-ID: <20030123170745.GA10829@khms.westfalen.de> (raw)

Debian testing/unstable
Linux khms.westfalen.de 2.4.19+kai.58 #1 Sam Sep 7 14:16:44 CEST 2002 i686 AMD Athlon(tm) Processor AuthenticAMD GNU/Linux
glibc Version: 2.3.1-10

Configure arguments:
--prefix=/opt/gcc-head --enable-multilib --enable-checking --enable-c-mbchar --enable-threads --enable-objc-gc --enable-nls --enable-version-specific-runtime-libs --enable-languages=all

End of log:
[...]
stage1/xgcc -Bstage1/ -B/opt/gcc-head/i686-pc-linux-gnu/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -fno-common -Werror   -DHAVE_CONFIG_H    -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/c-pch.c -o c-pch.o
stage1/xgcc -Bstage1/ -B/opt/gcc-head/i686-pc-linux-gnu/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -fno-common -Werror   -DHAVE_CONFIG_H    -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/cpplib.c -o cpplib.o
stage1/xgcc -Bstage1/ -B/opt/gcc-head/i686-pc-linux-gnu/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -fno-common -Werror   -DHAVE_CONFIG_H    -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/cpplex.c -o cpplex.o
../../gcc/gcc/cpplex.c: In function `cpp_interpret_charconst':
../../gcc/gcc/cpplex.c:1940: warning: pointer targets in passing arg 2 of `local_mbtowc' differ in signedness
make[2]: *** [cpplex.o] Fehler 1
make[2]: Leaving directory `/Partition/gcc/gcc/build/build/gcc'
make[1]: *** [stage2_build] Fehler 2
make[1]: Leaving directory `/Partition/gcc/gcc/build/build/gcc'
make: *** [bootstrap] Fehler 2

             reply	other threads:[~2003-01-23 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 19:59 Kai Henningsen [this message]
2003-01-24  0:44 ` Kaveh R. Ghazi
  -- strict thread matches above, loose matches on Subject: below --
2003-09-12 12:38 Mainline " S. Bosscher
2003-09-12 18:55 ` H. J. Lu
2003-09-12 12:28 Andreas Schwab
2002-08-31  8:52 Andreas Schwab
2002-08-31 14:12 ` Richard Henderson

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=20030123170745.GA10829@khms.westfalen.de \
    --to=kai@qualify.domain.khms.westfalen.de \
    --cc=gcc@gcc.gnu.org \
    --cc=kai@qualify.recipient.khms.westfalen.de \
    /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).