Re: Solaris and sed: Too many commands, last: s/\n//
- Date: Mon, 11 Mar 2019 20:18:26 -0400
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Subject: Re: Solaris and sed: Too many commands, last: s/\n//
On Mon, Mar 11, 2019 at 7:52 PM Jeffrey Walton <noloader@xxxxxxxxx> wrote:
> On Mon, Mar 11, 2019 at 5:15 PM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote:
> > [cc:+Ævar]
> > 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'".
> Yeah, you're right:
> $ make test V=1
> gmake -C t/ all
> gmake: 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.
I was not exporting PATH, so that was my mistake.
However, PATH is now exported but I get the same result.
Is the build system clearing the environment?