All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Brad Smith <brad@comstyle.com>
Cc: git@vger.kernel.org
Subject: Re: Solaris sed
Date: Wed, 11 Jun 2025 20:42:26 -0700	[thread overview]
Message-ID: <87bjqteicd.fsf@gmail.com> (raw)
In-Reply-To: <09f954b8-d9c3-418f-ad4b-9cb9b063f4ae@comstyle.com>

Hi Brad,

Brad Smith <brad@comstyle.com> writes:

> Building on Solaris I noticed the following two issues with Solaris sed.
>
>     GEN version-def.h
> sed: Missing newline at end of file standard input.
>
>     GEN config-list.h
> sed: illegal option -- E
> Usage:  sed [-n] script [file...]
>         sed [-n] [-e script]...[-f script_file]...[file...]
>
>
> https://github.com/git/git/commit/e1b81f54da80267edee2cb8fd0d0f75f03023019
>
> The second issue being introduced fairly recently. Not sure what would be
> appropriate fixes. Just pointing them out if someone has an suggestions for
> fixes.

I noticed these as well, but just ignored them since it seems to build
fine.

The first one seems like just a warning? Probably something to do with
POSIX defining a "Text File" as "A file that contains characters
organized into zero or more lines" where a line is "A sequence of zero
or more non- <newline> characters plus a terminating <newline>
character."

The second is more tricky. The '-E' option to use EREs was not added to
the specification for 'sed' until POSIX.1-2024 [1]. Maybe the script
could check for the 'gsed' command? All of the (few) Solaris machines I
use will have many GNU programs installed like that.

Collin

[1] https://pubs.opengroup.org/onlinepubs/9799919799/utilities/sed.html

  reply	other threads:[~2025-06-12  3:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  3:23 Solaris sed Brad Smith
2025-06-12  3:42 ` Collin Funk [this message]
2025-06-12  3:49   ` Brad Smith
2025-06-12  4:16     ` Eli Schwartz
2025-06-12  4:25       ` Collin Funk
2025-06-12  4:26       ` Brad Smith
2025-06-12  4:03 ` Junio C Hamano
2025-06-12  4:13   ` Brad Smith
2025-06-12  4:19     ` Collin Funk
2025-06-13 20:13       ` Jean-Noël AVILA
2025-06-13 20:23         ` Eric Sunshine
2025-06-13 20:30         ` Collin Funk
2025-06-12  5:50   ` Eric Sunshine
2025-06-12 13:35     ` Paul Smith
2025-06-12 16:40       ` Eric Sunshine
  -- strict thread matches above, loose matches on Subject: below --
2025-06-12 22:52 Ben Knoble

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=87bjqteicd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.