This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Ilya Basin <basinilya at gmail dot com>
Cc: Oleg Endo <oleg dot endo at t-online dot de>, gcc-help at gcc dot gnu dot org
Date: Mon, 8 Oct 2012 12:02:27 +0100
Subject: Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
References: <133615603.20121008141915@gmail.com> <1349692028.21984.36.camel@yam-132-YW-E178-FTW> <82245657.20121008143258@gmail.com>

On 8 October 2012 11:32, Ilya Basin wrote:
> Is there a flag to turn this warning into an error? Is there a common
> way to find the warning flag from a message?

If you use a modern version of GCC it tells you the flag that controls
each warning.

In this case it tells you it is "enabled by default" so there is no
flag controlling this warning.

References:
- Why "'X' used but never defined" is a warning and not error in gcc?
  - From: Ilya Basin
- Re: Why "'X' used but never defined" is a warning and not error in gcc?
  - From: Oleg Endo
- Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  - From: Ilya Basin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]