From: Miklos Vajna <vmiklos@frugalware.org>
To: Corey Stup <coreystup@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Compiler requirements for git?
Date: Wed, 14 Jan 2009 23:38:32 +0100 [thread overview]
Message-ID: <20090114223832.GC30710@genesis.frugalware.org> (raw)
In-Reply-To: <128172e70901141032p6e830a85i344d72e1b3bb3a89@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
On Wed, Jan 14, 2009 at 01:32:56PM -0500, Corey Stup <coreystup@gmail.com> wrote:
> When trying to compile with a C89 compliant compiler, I'm coming
> across a couple issues:
> - "inline" use
AFAIK that can be avoided with -Dinline=.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-14 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 18:32 Compiler requirements for git? Corey Stup
2009-01-14 22:38 ` Miklos Vajna [this message]
2009-03-14 1:04 ` [PATCH] Autoconf: Disable inline for compilers that don't support it Allan Caffee
2009-03-14 20:46 ` Junio C Hamano
2009-03-15 15:21 ` Allan Caffee
2009-03-15 19:52 ` Junio C Hamano
2009-03-16 22:31 ` Allan Caffee
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=20090114223832.GC30710@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=coreystup@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).