From: Junio C Hamano <gitster@pobox.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] Teach Solaris that _XOPEN_SOURCE=600 really menas XPG6
Date: Thu, 11 Jun 2009 08:58:46 -0700 [thread overview]
Message-ID: <7vmy8eiwy1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <B96700A1-EC8C-4DDE-A158-CE298FCCA09F@dbservice.com> (Tomas Carnecky's message of "Thu\, 11 Jun 2009 17\:06\:00 +0200")
Tomas Carnecky <tom@dbservice.com> writes:
> Until this commit a simple 'make prefix=...' worked just fine. Now I
> have to explicitly add '-std=c99' to the gcc commandline. Is there a
> reason why the makefile doesn't add this switch automatically?
An extended "Solaris updates" series has been cooking in 'next' branch, I
think, and does things a bit differently.
4cb18a4 (git-compat-util.h: tweak the way _XOPEN_SOURCE is set on Solaris,
2009-06-05) sets _XOPEN_SOURCE to 500 if you are not compiling with c99.
prev parent reply other threads:[~2009-06-11 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 19:24 [RFC/PATCH 0/2] OpenSolaris 2008.11 portability fixes Junio C Hamano
2009-05-23 19:24 ` [RFC/PATCH 1/2] Teach Solaris that _XOPEN_SOURCE=600 really menas XPG6 Junio C Hamano
2009-05-23 19:24 ` [RFC/PATCH 2/2] OpenSolaris 200811 (SunOS 5.11) does not want OLD_ICONV Junio C Hamano
2009-05-28 16:46 ` [RFC/PATCH 1/2] Teach Solaris that _XOPEN_SOURCE=600 really menas XPG6 Brandon Casey
2009-05-28 19:19 ` Jeff King
2009-05-28 19:40 ` Brandon Casey
2009-05-28 19:50 ` Jeff King
2009-05-28 20:37 ` Junio C Hamano
2009-06-11 15:06 ` Tomas Carnecky
2009-06-11 15:50 ` Brandon Casey
2009-06-11 16:42 ` Tomas Carnecky
2009-06-11 17:13 ` Brandon Casey
2009-06-11 17:36 ` Tomas Carnecky
2009-06-11 17:42 ` Brandon Casey
2009-06-11 15:58 ` Junio C Hamano [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmy8eiwy1.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).