public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: vannoy@pepperdine.edu
To: gcc-gnats@gcc.gnu.org
Subject: other/2998: "function.c: 7030: missing #endif" when building for SunOS 4.1.4
Date: Wed, 30 May 2001 00:36:00 -0000	[thread overview]
Message-ID: <20010530072750.2722.qmail@sourceware.cygnus.com> (raw)

>Number:         2998
>Category:       other
>Synopsis:       "function.c: 7030: missing #endif" when building for SunOS 4.1.4
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 30 00:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     John Vannoy
>Release:        gcc version 2.95.3 20010315 (release)
>Organization:
>Environment:
SunOS 4.1.4
>Description:
function.c has an indented #endif on line 6930.

The ancient C compiler supplied with SunOS 4.1.4
(and probably other systems) doesn't
recognize preprocessor directives unless they're in the
first column, so stage1 build fails with
".../gcc/function.c: 7030: missing #endif".
>How-To-Repeat:

>Fix:
Simple fix -- just unindent line 6930:

*** function.c.GCC295   Thu Jan 25 06:03:15 2001
--- function.c  Sat May 26 02:09:35 2001
***************
*** 6927,6933 ****
            }
        }
        }
!   #endif
  }
  
  /* Reposition the prologue-end and epilogue-begin notes after instruction
--- 6927,6933 ----
            }
        }
        }
! #endif
  }
  
  /* Reposition the prologue-end and epilogue-begin notes after instruction
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2001-05-30  0:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010530072750.2722.qmail@sourceware.cygnus.com \
    --to=vannoy@pepperdine.edu \
    --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).