My name is Hiroyuki NISHIMURA.
Thank you for your kindness.
I try three ways under the environmets LC_ALL=C and LANG=C.
1. Using /usr/bin/sed
Details
-r-xr-xr-x 1 root 28976 Dec 10 2002 /usr/bin/sed
108fb559f93421c70ce924fc95a3564a /usr/bin/sed
Sun's sed
Result
No Good
testsuite: 97 failed
2. Using /opt/sfw/bin/gsed
Details
-r-xr-xr-x 1 root 57116 Feb 19 2001 /opt/sfw/bin/gsed
2593d88841398bddc46b68123e5bd6f3 /opt/sfw/bin/gsed
GNU sed version 3.02
Result
No Good
testsuite: 97 failed
3. Using /usr/local/bin/sed
Details
-rwxr-xr-x 1 root 109020 Mar 1 19:15 /usr/local/bin/sed
794f10b0435e9d6054c8ef17641277c9 /usr/local/bin/sed
GNU sed version 4.1.5
Result
No Problem
As things turned out, I succeed.
Best Regard,
--
Hiroyuki NISHIMURA <[EMAIL PROTECTED]>
> Hiroyuki NISHIMURA <[EMAIL PROTECTED]> writes:
>
> > I am afraid that I think Sun's sed is No Good, GNU sed is Good.
>
> I cannot reproduce the problem on my Solaris 9 sparc host. Perhaps
> you need to patch your Solaris installation? Here's the 'sed' I have:
>
> 136-pete $ ls -l /usr/bin/sed
> -r-xr-xr-x 1 root bin 28976 Dec 9 2002 /usr/bin/sed
> 137-pete $ md5sum /usr/bin/sed
> 108fb559f93421c70ce924fc95a3564a /usr/bin/sed
>
> but I suppose it could be a library problem, too.
>
> Or maybe it's your locale? (Just guessing.)
