public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: ssathyan@india.smartstorage.com
Cc: egcs@egcs.cygnus.com
Subject: Re: How to make gcc print messages during compilation.
Date: Fri, 30 Jun 2000 10:24:00 -0000	[thread overview]
Message-ID: <200006301716.TAA01045@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <OFC54936BC.A32B4401-ON8525690E.00760DC7@india.smartstorage.com>

> (1) How we can make gcc to print user messages during the compilation
> process.

With the #error directive, or with the #warning directive.

> (2) Is there a way I can stop the compilation with error messages Like
> #error preprocessor directive in VC++ compilers.

Yes, the #error directive. That's not a MSVC invention - it is part of
the international standard.

>  (3) Is there a good book or web site which gives a good documentation of
> how to use gcc. Apart from man and info.

There is a gcc manual available, which you can order from the
FSF. However, it is the same material as the texinfo documentation.

Please note that gcc, in general, aims at implementing the relevant
standards for the languages it supports. So any good book on the
language is also a good book for GCC usage. In this particular case, a
good book on C or C++ would have told you that you can rely on #error
being there in every self-respecting compiler.

Regards,
Martin

      parent reply	other threads:[~2000-06-30 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-30  8:47 ssathyan
2000-06-30  9:02 ` Bolan Meek
2000-06-30 10:24 ` Martin v. Loewis [this message]

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=200006301716.TAA01045@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=egcs@egcs.cygnus.com \
    --cc=ssathyan@india.smartstorage.com \
    /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).