public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: kai@qualify.domain.khms.westfalen.de
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: mainline bootstrap failure
Date: Fri, 24 Jan 2003 00:44:00 -0000	[thread overview]
Message-ID: <200301231956.OAA11982@caip.rutgers.edu> (raw)
In-Reply-To: <20030123170745.GA10829@khms.westfalen.de>

 > 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/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

Fixed with this patch.  Patch tested via three-stage compile on
sparc-sun-solaris2.7 with configure flags --enable-languages=c
--disable-checking --disable-nls --enable-multilib=no
--enable-c-mbchar.

Installed as obvious.


2003-01-23  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>

	* cpplex.c (cpp_interpret_charconst): Squelch warning with cast.

diff -rup orig/egcc-CVS20030123/gcc/cpplex.c egcc-CVS20030123/gcc/cpplex.c
--- orig/egcc-CVS20030123/gcc/cpplex.c	2003-01-17 22:01:57.000000000 -0500
+++ egcc-CVS20030123/gcc/cpplex.c	2003-01-23 14:38:50.817748000 -0500
@@ -1937,7 +1937,7 @@ cpp_interpret_charconst (pfile, token, p
       wchar_t wc;
       int char_len;
 
-      char_len = local_mbtowc (&wc, str, limit - str);
+      char_len = local_mbtowc (&wc, (const char *)str, limit - str);
       if (char_len == -1)
 	{
 	  cpp_error (pfile, DL_WARNING,

  reply	other threads:[~2003-01-23 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 19:59 Kai Henningsen
2003-01-24  0:44 ` Kaveh R. Ghazi [this message]
  -- 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=200301231956.OAA11982@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kai@qualify.domain.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).