public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mtodorov@alu.hr To: gcc-gnats@gcc.gnu.org Subject: c/2751: Spurious warnings in gcc 2.95.3 <stdarg.h> include files Date: Sun, 06 May 2001 06:36:00 -0000 [thread overview] Message-ID: <20010506132610.14325.qmail@sourceware.cygnus.com> (raw) >Number: 2751 >Category: c >Synopsis: Spurious warnings in gcc 2.95.3 <stdarg.h> include files >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun May 06 06:36:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Mirsad Todorovac >Release: gcc-2.95.3 >Organization: >Environment: alpha-osf-4.0b GNU make 3.79 tcsh 6.10.00 >Description: In every more complex program compiled, when <stdarg.h> is included, this type of warnings occur. I couldn't see an example that a program was wrong-compiled beacuse of this, but on the other hand no evidence exists that there are no errors in compilation indicated by this warnings. Example: gcc -I../ncurses -I. -DNDEBUG -I. -I../include -I/usr/local/include/ncurses -DHAVE_CONFIG_H -O2 -c ../ncurses/./tty/hashmap.c -DPIC -o .libs/hashmap.lo In file included from /usr/local/lib/gcc-lib/alpha-dec-osf4.0b/2.95.3/include/stdarg.h:36, from ../include/curses.h:80, from ../ncurses/curses.priv.h:236, from ../ncurses/./tty/hashmap.c:70: /usr/local/lib/gcc-lib/alpha-dec-osf4.0b/2.95.3/include/va-alpha.h:36: warning: redefinition of `va_list' /usr/local/lib/gcc-lib/alpha-dec-osf4.0b/2.95.3/include/va_list.h:7: warning: `va_list' previously declared here >How-To-Repeat: When building gcc-2.95.3, use default, fast fixinclude mechanism. I haven't checked out whether the error occurs when older fixinclude scripts are used. >Fix: ? >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-05-06 6:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-06 6:36 mtodorov [this message] 2002-04-23 1:58 rth
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=20010506132610.14325.qmail@sourceware.cygnus.com \ --to=mtodorov@alu.hr \ --cc=gcc-gnats@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: linkBe 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).