public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: rbrown64@csc.com.au
To: kenner@vlsi1.ultra.nyu.edu, <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: Serious internationalization problems: revert?
Date: Fri, 19 Oct 2001 08:23:00 -0000	[thread overview]
Message-ID: <OF26683622.B93E5607-ONCA256AEA.0052A6D4@int.csc.com.au> (raw)

>A recent change introduced three problems:

>(1) In some configurations, intl.h is not found.
>(2) Some configurations complain that make can't find -liconv, since
    it gets erroneously considered a dependency.
>(3) There are dozens of warnings about missing declarations and format
    arg mismatches.

>Is anybody working on this or is it time to consider reverting those
changes?

Wrt (1) at least CVS Wed Oct 17 23:03:18 UTC 2001 is working for me
on i686-unknown-sysv5UnixWare7.1.0 which had been failing for me before.


I needed to follow Zack's instructions, running autoconf and autoheader
again
and also found I needed to remove config.cache. make distclean didn't cut
it.
Maybe maintainerclean would have.

My setup is screwy though. Hope this helps

--- 1011/warning.log    Fri Oct 12 12:02:09 2001 (UnixWare 7.1 3.1)
+++ ./warning.log       Sat Oct 20 01:23:27 2001
@@ -1,38 +1,50 @@
 Counting all warnings,
-there are 89 warnings in stage3 of this bootstrap.
+there are 139 warnings in stage3 of this bootstrap.

 Number of warnings per file:
+28 gcc/intl/gettextP.h
 23 gcc/combine.c
+18 gcc/intl/loadmsgcat.c
 18 gcc/dwarfout.c
-8 gcc/langhooks.c
 7 gcc/varasm.c
 6 gcc/cp/pt.c
+5 gcc/intl/localealias.c
 5 gcc/cse.c
+4 gcc/intl/l10nflist.c
 4 gcc/gcc.c
 2 gcc/tlink.c
 2 gcc/objc/objc-act.c
-2 gcc/java/lang.c
+2 gcc/intl/localcharset.c
+2 gcc/intl/dcigettext.c
 2 gcc/fold-const.c
-2 gcc/f/com.c
+1 plural.y
+1 insn-emit.c
 1 gcc/rtlanal.c
+1 gcc/regmove.c
 1 gcc/objc/lang-specs.h
 1 gcc/java/jvspec.c
-1 gcc/intl/localealias.c
-1 gcc/intl/dcgettext.c
 1 gcc/f/lang-specs.h
+1 gcc/dwarf2out.c
 1 gcc/dwarf2asm.c
+1 gcc/cp/lex.c
 1 gcc/cp/lang-specs.h

 Number of warning types:
-54 comparison between signed and unsigned
-8 function declaration isn't a prototype
+57 comparison between signed and unsigned
+17 function declaration isn't a prototype
+15 ISO C forbids zero-size array `???'
+12 ISO C89 forbids specifying subobject to initialize
+9 subscript has type `char'
 7 string length `???' is greater than the length `???' ISO C89 compilers
are re
quired to support
 6 ??? format, ??? arg (arg ???)
-3 missing initializer
-3 (near initialization for `???')
+2 traditional C rejects initialization of unions
 2 passing arg ??? of `???' discards qualifiers from pointer target type
+2 missing initializer
 2 implicit declaration of function `???'
+2 (near initialization for `???')
+1 unused parameter `???'
 1 suggest not using #elif in traditional C
 1 signed and unsigned type in conditional expression
+1 right shift count >= width of type
 1 pointer targets in passing arg ??? of `???' differ in signedness
 1 `???' defined but not used

             reply	other threads:[~2001-10-19  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19  8:23 rbrown64 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-19 10:20 Richard Kenner
2001-10-19 10:23 ` gcc
2001-10-19  8:30 Richard Kenner
2001-10-19  8:47 ` Zack Weinberg
2001-10-19  5:30 Richard Kenner
2001-10-19  4:21 Richard Kenner
2001-10-19  4:29 ` Gerald Pfeifer
2001-10-19  5:14   ` Richard Earnshaw
2001-10-19  8:20 ` Zack Weinberg

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=OF26683622.B93E5607-ONCA256AEA.0052A6D4@int.csc.com.au \
    --to=rbrown64@csc.com.au \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).