All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Remove more gcc extension usage.
Date: Mon, 10 Jul 2006 01:22:55 -0400	[thread overview]
Message-ID: <20060710052255.GA15173@spearce.org> (raw)
In-Reply-To: <20060709073155.GP22573@lug-owl.de>

> On Sat, 2006-07-08 15:03:27 -0400, Shawn Pearce <spearce@spearce.org> wrote:
> > Monday I'll look to see if there's an option that can be given to
> > the Solaris compiler to make it accept these constructs.  Maybe a
> > simple CFLAGS change in my config.mak would resolve what this patch
> > was trying to do.

So Monday turned out to be today.  The compiler version:

  $ cc -V                                                        
  cc: Forte Developer 7 C 5.4 2002/03/09
  usage: cc [ options] files.  Use 'cc -flags' for details

and from `man cc`:

  -xc99  enables C99 features:

          The following is a list of the implemented features of
          the ISO/IEC 9899:1999, Programming Language - C stan-
          dard. See the C User's Guide for a detailed explanation
          of the compiler's support for these featuers:

          o  Idempotent Qualifiers
          o  _Pragma
          o  Mixed Declarations and Code
          o  static and Other Type Qualifiers Allowed in Array
             Declarators
          o  Flexible Array Members
          o  Declarations Using Implicit int
          o  Disallowed Implicit int and Implicit Function
             Declarations
          o  Declaration in for-Loop Statement
          o  C99 Keywords
          o  __func__ Support
          o  Macros With A Variable Number of Arguments
          o  Variable Length Arrays
          o  inline Specifier For Static Functions
          o  Commenting Code with //

So neither of the constructs my patch removes are supported in this
(old) compiler, although a newer one might accept them with -xc99.
Yes, I tried building a pristine git-1.4.1 with -xc99.  It barfed,
as one would expect given the description above.

Since we don't have a newer version of cc available (not sure why)
I'm stuck with needing to make the code changes in my patch just
to get GIT to compile.

-- 
Shawn.

  reply	other threads:[~2006-07-10  5:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 18:34 [PATCH] Remove more gcc extension usage Shawn Pearce
2006-07-08 18:51 ` Junio C Hamano
2006-07-08 19:03   ` Shawn Pearce
2006-07-09  7:31     ` Jan-Benedict Glaw
2006-07-10  5:22       ` Shawn Pearce [this message]
2006-07-10  6:14         ` Jan-Benedict Glaw
2006-07-10  6:22         ` Pavel Roskin
2006-07-10  6:25           ` Jan-Benedict Glaw
2006-07-10  6:52             ` Pavel Roskin
2006-07-10  7:35               ` Jan-Benedict Glaw
2006-07-10  8:07                 ` Pavel Roskin
2006-07-10  8:10                   ` Junio C Hamano
2006-07-10  8:18                   ` Jan-Benedict Glaw
2006-07-10  7:47           ` Junio C Hamano
2006-07-12 13:46         ` Paul Jakma

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=20060710052255.GA15173@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jbglaw@lug-owl.de \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.