public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/53677] New: GNAT build didn't stop after a fatal error
Date: Thu, 14 Jun 2012 22:52:00 -0000	[thread overview]
Message-ID: <bug-53677-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53677

             Bug #: 53677
           Summary: GNAT build didn't stop after a fatal error
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: tschwinge@gcc.gnu.org


Working on a GNU/Hurd for for GCC Ada/GNAT, I stumbled over the following
issue (which I believe not to be specific to the GNU/Hurd port).

I botched up an edit of gcc/ada/s-oscons-tmplt.c (mismatched parentheses;
I tried adding the __GNU__ conditional next to the __linux__ one).  In
the build log I could see the following error message:

    [...]/gcc/ada/s-oscons-tmplt.c:83:5: error: missing ')' in expression
     #if (defined (__linux__) || defined (__GNU__) && !defined (_XOPEN_SOURCE)
         ^
    make -C rts \
                    CC=[...]

However -- as this snippet also shows -- the GNAT build didn't stop at
this point, which I believe it should have, as this is a "hard" syntax
error.


And what is perhaps even more bewildering is that despite this fatal
error, the build successfully continued up to the very end, and even the
make check run produced totally sensible results.  I understand that
s-oscons-tmplt.c is used for generating the package System.OS_Constants,
but how can this have been done successfully if building that file
failed?


             reply	other threads:[~2012-06-14 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 22:52 tschwinge at gcc dot gnu.org [this message]
2012-06-17  7:51 ` [Bug ada/53677] " ebotcazou at gcc dot gnu.org
2014-02-22  8:42 ` ebotcazou at gcc dot gnu.org
2014-02-22  8:43 ` ebotcazou at gcc dot gnu.org

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=bug-53677-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).