From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: There seems to be a problem with the test harness on Solaris 11.4
Date: Sun, 6 Nov 2022 13:32:00 -0600 [thread overview]
Message-ID: <d56974f8-f0c2-19e1-04c9-d236071d86bc@zentaur.org> (raw)
In-Reply-To: <CAH+w=7YmTOJ3BDFzZfvp-mRFyGpM3STbxv0yxNpFF4=h=rq2Gg@mail.gmail.com>
On 11/6/2022 1:09 PM, Bart Schaefer wrote:
> On Sun, Nov 6, 2022 at 10:35 AM Clinton Bunch <cdb_zsh@zentaur.org> wrote:
>> Solaris 11.4 at least also has GNU diff as gdiff.
> Use of "diff -a" hasn't changed since at least 2017. Is it possible
> that there's been a default (or your own) PATH change causing the
> POSIX diff to be found in preference?
>
I haven't changed the default path on this system yet. To get GNU diff
as diff you'd have to add /usr/gnu/bin to the path, and I doubt that's
been in the standard path. I'm not positive it wasn't pulled in as a
prereq when I installed autoconf from the standard package repository.
I think it's possible that only a few people have run the tests on
Solaris in the last 5 years and either had /usr/gnu/bin in their path
(not exactly unexpected from someone who'd try to build their own shell)
or they just didn't report the failure.
Especially since it ships with a version of zsh (5.3.1), a lot of people
wouldn't feel the need to build their own.
next prev parent reply other threads:[~2022-11-06 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 16:54 Clinton Bunch
2022-11-06 18:12 ` Bart Schaefer
2022-11-06 18:28 ` Clinton Bunch
2022-11-06 18:34 ` Clinton Bunch
2022-11-06 19:09 ` Bart Schaefer
2022-11-06 19:32 ` Clinton Bunch [this message]
2022-11-07 19:39 ` Clinton Bunch
2022-11-09 3:29 ` [PATCH] diff for test harness (was: There seems to be a problem with the test harness on Solaris 11.4) Clinton Bunch
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=d56974f8-f0c2-19e1-04c9-d236071d86bc@zentaur.org \
--to=cdb_zsh@zentaur.org \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).