From: Jeffrey Walton <noloader@gmail.com>
Date: Mon, 11 Mar 2019 23:52:54 GMT
Subject: Re: Solaris and sed: Too many commands, last: s/\n//
Message-ID: <CAH8yC8=YrZR=j9R8Ae+O2UzfxB_Hc1Osu68T-M1mczHiEasfJQ@mail.gmail.com>
In-Reply-To: <CAPig+cTCOfDCv=L3EWUqgVZx1VCdqt5ZjmSQMwHLX=R4C4hgTA@mail.gmail.com>

On Mon, Mar 11, 2019 at 5:15 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
>
> [cc:+Ævar]
>
> On Mon, Mar 11, 2019 at 4:32 PM Jeffrey Walton <noloader@gmail.com> wrote:
> > I enabled self tests for Solaris. Solaris has some anemic utilities so
> > I put /usr/gnu/bin first on-path.
>
> The first question is if you are really running GNU 'sed'? My guess is
> "no, it's still picking up Solaris's 'sed'".

Yeah, you're right:

$ make test V=1
...

gmake -C t/ all
gmake[1]: Entering directory `/export/home/jwalton/Build-Scripts/git-2.21.0/t'
rm -f -r 'test-results'
SED VERSION: sed: illegal option -- version

I wonder why ... Let me check if I am exporting PATH.

Jeff