From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Jeffrey Walton <noloader@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Solaris and sed: Too many commands, last: s/\n//
Date: Tue, 12 Mar 2019 10:08:29 +0100 [thread overview]
Message-ID: <87zhq0bgtu.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAPig+cTCOfDCv=L3EWUqgVZx1VCdqt5ZjmSQMwHLX=R4C4hgTA@mail.gmail.com>
On Mon, Mar 11 2019, Eric Sunshine 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'".
>
>> gmake -C templates SHELL_PATH='/bin/bash' PERL_PATH='/usr/bin/perl'
>> sed: Too many commands, last: s/\n//
>> --- chainlint/arithmetic-expansion.expect 2019-02-24
>
> Ævar had taken a stab at getting this to work on Solaris back in
> September 2018. He did fix one or two issues, but the one you report
> here was not addressed. He ultimately abandoned the attempt, I think,
> after Junio's reminder that the project had long ago declared
> Solaris's tools as a lost cause. See the relevant messages:
>
> http://public-inbox.org/git/87bm9cs5y6.fsf@evledraar.gmail.com/
> http://public-inbox.org/git/CAPig+cRrwW662Hzp8V1sH51x8qYxPyqG=VHpOkfd-=RwUSSZbw@mail.gmail.com
> http://public-inbox.org/git/877ek0rymz.fsf@evledraar.gmail.com
> http://public-inbox.org/git/xmqqzhwv51wy.fsf@gitster-ct.c.googlers.com
>
>> Solaris in a VM sucks. I can provide SSH access to the hardware if
>> anyone is interested. It is just an Solaris i86pc on an older Ivy
>> Bridge.
>
> I wouldn't mind taking a look at it, though I don't promise anything,
> and I suspect the only way forward is by ensuring that the GNU or XPG
> tools are used instead of the Solaris ones.
FWIW I gave up on Solaris sed after trying to fix it the last time
around.
If you need another box to test it on you can apply for a GCC Farm
account: https://cfarm.tetaneutral.net/machines/list/
prev parent reply other threads:[~2019-03-12 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 20:31 Solaris and sed: Too many commands, last: s/\n// Jeffrey Walton
2019-03-11 21:15 ` Eric Sunshine
2019-03-11 21:43 ` Jeffrey Walton
2019-03-11 22:28 ` Eric Sunshine
2019-03-12 1:07 ` Jeffrey Walton
2019-03-12 1:55 ` Jeffrey Walton
2019-03-12 2:11 ` Jeffrey Walton
2019-03-12 2:19 ` Jeffrey Walton
2019-03-12 2:45 ` Eric Sunshine
2019-03-12 3:57 ` Jeffrey Walton
2019-03-11 23:52 ` Jeffrey Walton
2019-03-12 0:18 ` Jeffrey Walton
2019-03-12 9:08 ` Ævar Arnfjörð Bjarmason [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhq0bgtu.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.com \
--cc=sunshine@sunshineco.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).