Re: Solaris and sed: Too many commands, last: s/\n//
- Date: Mon, 11 Mar 2019 21:07:44 -0400
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Subject: Re: Solaris and sed: Too many commands, last: s/\n//
On Mon, Mar 11, 2019 at 6:28 PM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote:
> On Mon, Mar 11, 2019 at 05:43:55PM -0400, Jeffrey Walton wrote:
> > On Mon, Mar 11, 2019 at 5:15 PM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote:
> > > On Mon, Mar 11, 2019 at 4:32 PM Jeffrey Walton <noloader@xxxxxxxxx> 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'".
> > I believe so. After modifying PATH, command -v returns:
> > Solaris tools:
> > sed: /usr/gnu/bin/sed
> > awk: /usr/gnu/bin/awk
> > grep: /usr/gnu/bin/grep
> > (This was added to my scripts to confirm).
> > Maybe Git would benefit from SED, AWK and GREP variables like PERL.
> Very possibly.
Another potential workaround is to use Perl. Perl is already a
prerequisite, it get passed to the test gear through PERL_PATH, and it
avoids Solaris' anemic tools.
Sadly my Perl sucks. You would be disappointed if I tried to whip up a patch.