From: Collin Funk <collin.funk1@gmail.com>
To: Brad Smith <brad@comstyle.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] config.mak.uname: update settings for FreeBSD
Date: Wed, 11 Jun 2025 20:31:36 -0700 [thread overview]
Message-ID: <87ikl1eiuf.fsf@gmail.com> (raw)
In-Reply-To: <aEpF3ZjNwkR8FssX@humpty.home.comstyle.com>
Hi Brad,
Brad Smith <brad@comstyle.com> writes:
> FreeBSD 6.0 has memmem().
>
> Signed-off-by: Brad Smith <brad@comstyle.com>
> ---
> config.mak.uname | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/config.mak.uname b/config.mak.uname
> index b1c5c4d5e8..da592eeaa0 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -302,16 +302,10 @@ ifeq ($(uname_S),FreeBSD)
> ifeq ($(firstword $(subst -, ,$(uname_R))),10.1)
> OLD_ICONV = YesPlease
> endif
> - NO_MEMMEM = YesPlease
I don't have a FreeBSD machine that old to test it. But Gnulib's
documentation says it was added in FreeBSD 5.2.1 [1].
Reviewed-by: Collin Funk <collin.funk1@gmail.com>
> BASIC_CFLAGS += -I/usr/local/include
> BASIC_LDFLAGS += -L/usr/local/lib
> DIR_HAS_BSD_GROUP_SEMANTICS = YesPlease
> USE_ST_TIMESPEC = YesPlease
> - ifeq ($(shell expr "$(uname_R)" : '4\.'),2)
> - PTHREAD_LIBS = -pthread
> - NO_UINTMAX_T = YesPlease
> - NO_STRTOUMAX = YesPlease
> - endif
> PYTHON_PATH = /usr/local/bin/python
> PERL_PATH = /usr/local/bin/perl
> HAVE_PATHS_H = YesPlease
Curious about this change though. Are you basing it off a FreeBSD system
you have? Or do we not care about that old version anymore? For
reference, FreeBSD 4.2 was released in 2000.
Collin
[1] https://www.gnu.org/software/gnulib/manual/html_node/memmem.html
[2] https://www.freebsd.org/releases/4.2R/announce/
next prev parent reply other threads:[~2025-06-12 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 3:13 [PATCH] config.mak.uname: update settings for FreeBSD Brad Smith
2025-06-12 3:31 ` Collin Funk [this message]
2025-06-12 3:46 ` Brad Smith
2025-06-12 3:47 ` Junio C Hamano
2025-06-12 3:54 ` Brad Smith
2025-07-03 12:40 ` Renato Botelho
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=87ikl1eiuf.fsf@gmail.com \
--to=collin.funk1@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).