Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7188465
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T19:05:26+00:00 2026-05-28T19:05:26+00:00

GCC gives a warning implicit declaration of function foo when you use foo() before

  • 0

GCC gives a warning implicit declaration of function foo when you use foo() before its declaration. Is there any GCC flag that would make treat this warning as error and stop compilation? Sometime it would save you some debugging work…

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T19:05:27+00:00Added an answer on May 28, 2026 at 7:05 pm

    -Werror will treat all warnings as errors. You can be more specific with
    -Werror-implicit-function-declaration

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When i use gets function,gcc gives me a warning: warning:the `gets' function is dangerous
GCC seem to think that I am trying to make a function call in
I am trying to understand the difference in warning gives by gcc-4.3.2 and gcc-4.5.1.
If I declare and never use variable then gcc will give me a warning.
I have a piece of C code that looks like this: const char (*foo)[2]
I know this is wrong and gcc will give you a warning about it,
When trying to compile the example below, I received a warning: >gcc -o file
I have a problem with the unused local variable warning in GCC. Often I
Compiling with gcc 4.4.3 on Ubuntu 10.04.2 x86_64 I get the following warning: warning:
Turns out that g++ compiler (used in Qt Creator by default) gives a mere

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.