Re: stumped on a simple autoconf/m4/sh problem

"G. Branden Robinson" <[email protected]> Mon, 2 Dec 2024 14:26:41 -0600

Newsgroups	gmane.comp.sysutils.autoconf.general,gmane.comp.printing.groff.general
Message-ID	<20241202202641.qups4kauurq2t3jr@illithid>

Hi Paul,

At 2024-12-02T11:45:30-0800, Paul Eggert wrote:
> On 2024-12-01 19:03, G. Branden Robinson wrote:
> > The problem is that the test exercising `$cmd` succeeds on Solaris
> > 10 when it should not.
> 
> Why shouldn't the test succeed? Solaris 10 /usr/bin/tr supports
> character classes like [:cntrl:].

It doesn't for me in the instance at gcc210.fsffrance.org.

But it did occur to me that the '[ *]' argument might have been the
problem.  Here are my experiments.

bash-3.2$ type tr
tr is /usr/bin/tr
bash-3.2$ echo abc | tr 'ab' '[ *]'
  c
bash-3.2$ echo abc | tr '[:cntrl:]' '[ *]'
Bad string
bash-3.2$ what /usr/bin/tr
bash: what: command not found
bash-3.2$ ident /usr/bin/tr
bash: ident: command not found
bash-3.2$ tr -v
tr: illegal option -- v
Usage: tr [ -cds ] [ String1 [ String2 ] ]

I love these environments where you can't get a command to identify
its own provenance.  Must be "unpublished proprietary source code of
AT&T".  :-|

Regards,
Branden

signature.asc (application/pgp-signature, 833 B)