From: Brandon Casey <casey@nrlssc.navy.mil>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j6t@kdbg.org>, John Bito <jwbito@gmail.com>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] Makefile: use compat regex on Solaris
Date: Tue, 16 Jun 2009 15:07:40 -0500 [thread overview]
Message-ID: <v5GZyk1pvyw2mnFGX-8GiCIBKzquUZb5YYcjHNvgkczpXD2vQ4qdjg@cipher.nrlssc.navy.mil> (raw)
In-Reply-To: <20090616190821.GB23197@coredump.intra.peff.net>
Jeff King wrote:
> The system regex is either slow or buggy for complex
> patterns, like the built-in xfuncname pattern for java
> files.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> Rebased to today's master to resolve textual conflicts.
>
> Makefile | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 0cb21da..3bd0c08 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -725,6 +725,7 @@ ifeq ($(uname_S),SunOS)
> NO_MEMMEM = YesPlease
> NO_MKDTEMP = YesPlease
> NO_MKSTEMPS = YesPlease
> + NO_REGEX = YesPlease
> ifeq ($(uname_R),5.7)
> NEEDS_RESOLV = YesPlease
> NO_IPV6 = YesPlease
You need to add -DHAVE_ALLOCA_H to the BASIC_CFLAGS statement in
the SunOS section of the Makefile so that alloca.h will be included
in compat/regex/regex.c. This is necessary for the SUNWspro compiler.
It takes me a long time to compile, so I haven't checked yet whether
this causes any problems for the GNU compiler.
-brandon
next prev parent reply other threads:[~2009-06-16 20:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 1:37 git diff looping? John Bito
2009-06-16 2:44 ` Jeff Epler
2009-06-16 2:53 ` John Bito
2009-06-16 11:47 ` Jeff King
2009-06-16 12:07 ` Jeff King
2009-06-16 12:11 ` [PATCH 1/2] Makefile: refactor regex compat support Jeff King
2009-06-16 18:47 ` Johannes Sixt
2009-06-16 19:05 ` Jeff King
2009-06-16 19:07 ` [PATCH v2 " Jeff King
2009-06-16 19:08 ` [PATCH v2 2/2] Makefile: use compat regex on Solaris Jeff King
2009-06-16 20:07 ` Brandon Casey [this message]
2009-06-17 13:15 ` Mike Ralphson
2009-06-17 13:55 ` Mike Ralphson
2009-06-16 12:14 ` [PATCH " Jeff King
2009-06-16 15:48 ` git diff looping? John Bito
2009-06-16 16:51 ` Junio C Hamano
2009-06-16 17:15 ` Jeff King
2009-06-16 17:35 ` Brandon Casey
2009-06-16 17:39 ` John Bito
2009-06-16 17:41 ` Jeff King
2009-06-16 20:22 ` Brandon Casey
2009-06-17 8:46 ` Paolo Bonzini
2009-06-17 10:23 ` Jeff King
2009-06-17 11:02 ` Paolo Bonzini
2009-06-17 11:31 ` Andreas Ericsson
2009-06-17 13:08 ` Paolo Bonzini
2009-06-17 13:16 ` Andreas Ericsson
2009-06-17 13:58 ` Paolo Bonzini
2009-06-17 14:26 ` [PATCH] avoid exponential regex match for java and objc function names Paolo Bonzini
2009-06-17 15:46 ` demerphq
2009-06-17 15:56 ` Jeff King
2009-06-17 16:00 ` demerphq
2009-06-17 16:04 ` Paolo Bonzini
2009-06-17 16:42 ` Junio C Hamano
2009-06-18 6:45 ` Paolo Bonzini
2009-06-16 17:16 ` git diff looping? John Bito
2009-06-16 17:24 ` Jeff King
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=v5GZyk1pvyw2mnFGX-8GiCIBKzquUZb5YYcjHNvgkczpXD2vQ4qdjg@cipher.nrlssc.navy.mil \
--to=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jwbito@gmail.com \
--cc=peff@peff.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.
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).