git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Brad Smith <brad@comstyle.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] config.mak.uname: update settings for Solaris 11
Date: Sat, 7 Jun 2025 10:42:58 +0200	[thread overview]
Message-ID: <aEP7kpQIHZx94eg6@google.com> (raw)
In-Reply-To: <aEOlc_PV7ZngUdj0@humpty.home.comstyle.com>

Brad Smith wrote:

> Solaris 11.0 and newer have mkdtemp(), memmem(), strcasestr()
> and strtoumax().
>
> Signed-off-by: Brad Smith <brad@comstyle.com>
> ---
>  config.mak.uname | 28 +++++++++++++++++++++++++---
>  1 file changed, 25 insertions(+), 3 deletions(-)

Thanks!  That's from more than 10 years ago, so seems very reasonable
to rely on.  I assume this is tested :), so lgtm.

Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>

[...]
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -190,9 +190,6 @@ ifeq ($(uname_S),SunOS)
>  	SHELL_PATH = /bin/bash
>  	SANE_TOOL_PATH = /usr/xpg6/bin:/usr/xpg4/bin
>  	HAVE_ALLOCA_H = YesPlease
> -	NO_STRCASESTR = YesPlease
> -	NO_MEMMEM = YesPlease
> -	NO_MKDTEMP = YesPlease
>  	NO_REGEX = YesPlease
>  	NO_MSGFMT_EXTENDED_OPTIONS = YesPlease
>  	HAVE_DEV_TTY = YesPlease
> @@ -202,7 +199,10 @@ ifeq ($(uname_S),SunOS)
>  		NO_IPV6 = YesPlease
>  		NO_SOCKADDR_STORAGE = YesPlease
>  		NO_UNSETENV = YesPlease
> +		NO_MKDTEMP = YesPlease
> +		NO_MEMMEM = YesPlease
>  		NO_SETENV = YesPlease
> +		NO_STRCASESTR = YesPlease
>  		NO_STRLCPY = YesPlease
>  		NO_STRTOUMAX = YesPlease
>  		GIT_TEST_CMP = cmp
> @@ -212,23 +212,45 @@ ifeq ($(uname_S),SunOS)
>  		NO_IPV6 = YesPlease
>  		NO_SOCKADDR_STORAGE = YesPlease
>  		NO_UNSETENV = YesPlease
> +		NO_MKDTEMP = YesPlease
> +		NO_MEMMEM = YesPlease
>  		NO_SETENV = YesPlease
> +		NO_STRCASESTR = YesPlease
>  		NO_STRLCPY = YesPlease
>  		NO_STRTOUMAX = YesPlease
>  		GIT_TEST_CMP = cmp
>          endif
>          ifeq ($(uname_R),5.8)
>  		NO_UNSETENV = YesPlease
> +		NO_MKDTEMP = YesPlease
> +		NO_MEMMEM = YesPlease
>  		NO_SETENV = YesPlease
> +		NO_STRCASESTR = YesPlease
>  		NO_STRTOUMAX = YesPlease
>  		GIT_TEST_CMP = cmp
>          endif
>          ifeq ($(uname_R),5.9)
>  		NO_UNSETENV = YesPlease
> +		NO_MKDTEMP = YesPlease
> +		NO_MEMMEM = YesPlease
>  		NO_SETENV = YesPlease
> +		NO_STRCASESTR = YesPlease
>  		NO_STRTOUMAX = YesPlease
>  		GIT_TEST_CMP = cmp
>          endif
> +        ifeq ($(uname_R),5.10)
> +		NO_UNSETENV = YesPlease
> +		NO_MKDTEMP = YesPlease
> +		NO_MEMMEM = YesPlease
> +		NO_SETENV = YesPlease
> +		NO_STRCASESTR = YesPlease
> +		GIT_TEST_CMP = cmp
> +        endif
> +        ifeq ($(uname_R),5.11)
> +		NO_UNSETENV = YesPlease
> +		NO_SETENV = YesPlease
> +		GIT_TEST_CMP = cmp
> +        endif

Not about this change: do we want to retire some of the cases for old
versions at some point, or to collapse them so they can share more?
Seems nice for maintainability.

Sincerely,
Jonathan

  reply	other threads:[~2025-06-07  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  2:35 [PATCH] config.mak.uname: update settings for Solaris 11 Brad Smith
2025-06-07  8:42 ` Jonathan Nieder [this message]
2025-06-07 17:31   ` Junio C Hamano

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=aEP7kpQIHZx94eg6@google.com \
    --to=jrnieder@gmail.com \
    --cc=brad@comstyle.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).