public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bighead@users.sourceforge.net
To: gcc-gnats@gcc.gnu.org
Subject: c/7749: warning: no previous prototype for foobar_func ()
Date: Wed, 28 Aug 2002 12:56:00 -0000	[thread overview]
Message-ID: <20020828190230.13755.qmail@sources.redhat.com> (raw)


>Number:         7749
>Category:       c
>Synopsis:       warning: no previous prototype for foobar_func ()
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 28 12:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     bighead@users.sourceforge.net
>Release:        gcc-2.96
>Organization:
>Environment:
RedHat-7.2 system with gcc-2.96-98 (as revealed by "rpm -q gcc")
>Description:
When I compile a program using autoconf/automake I get a 
warning like "warning: no previous prototype for foobar_func"
when infact there is one.

Note: the command line reveals I'm compiling with most of the -W* options on. especially -Wall and -Wmissing-prototypes.

Weird thing is it happens for functions which take no parameters at all, or have a signature like foobar_func (void). Note: both cases.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-08-28 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 12:56 bighead [this message]
2003-03-11 22:36 neroden

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=20020828190230.13755.qmail@sources.redhat.com \
    --to=bighead@users.sourceforge.net \
    --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: 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).