Hi, Ryo!
Thanks very much for your helpful advice.
The problem was really due to the LANGUAGE. If it is in Chinese as I used before, the results are as follow:
% echo README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`
README_23 1月09
% env | grep LC_
% env | grep LANG
LANG=zh_CN.UTF-8
GDM_LANG=zh_CN.UTF-8
LANGUAGE=
% env | grep LOCALE
% setenv LANG C
% echo README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`
Hi Laura and Ferret developers,
I guess this error is from
| I am trying to install FERRET on my laptop. The system is Fedoral
| Core 9. I executed Finstall, chose 1 and give the path of
| "FER_DIR". However, it stopped after I gave the path of
| fer_executables.tar.Z, and showed:
|
| Moving to usr/local/ferret/bin...
| README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`: Ambiguous
echo "FERRET executables installed this date by $user" \
>! README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`
of Finstall. The cause of the error may that your "date" command
returns a string that contains white spaces or some non-ASCII
characters.
For example,
$ csh
% echo hello > `echo my file`
`echo my file`: Ambiguous.
% echo hello > `echo my-file`
% echo hello > README_`/bin/date +'%d %h%y'|tr '[A-Z]' '[a-z]'`
README_`/bin/date +'%d %h%y'|tr '[A-Z]' '[a-z]'`: Ambiguous.
%
Notice that I've deliberately inserted a white space between %d and %h.
Laura, I'm wondering if you could type this and report what's printed?
% echo README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`
% env | grep LC_
% env | grep LANG
% env | grep LOCALE
What about this?
% setenv LANG C
% echo README_`/bin/date +'%d%h%y'|tr '[A-Z]' '[a-z]'`
Ferret developers, the output of the "date" command depends on
locale. So, it's safe to set
setenv LANG C
at the top of a shell script.
Cheers,
Ryo