Akim Demaille wrote:
>
> | Eureka, quotes! Could you please test this construct:
> |
> | if $ac_need_defaults; then
> | : ${CONFIG_FILES="$config_files"}
> | fi
>
> No, this is not good. I removed the quotes on purpose.
>
> 2000-02-10 Akim Demaille <[EMAIL PROTECTED]>
>
> * acgeneral.m4 (_AC_OUTPUT_CONFIG_STATUS): Don't
> : ${FOO="$foo"}
> but
> : ${FOO=$foo}
> Since Ultrix will also assign the quotes to FOO.
> Reported by Harlan Stenn.
>
> David, what is your shell? It is seriously damaged :( This behavior,
> this *silent* behavior is incredible. What's your environment?
On the OS the shell is is called /bin/sh and is a link to /bin/ksh
I will make no comments about this being braindead but it is a QNX 4.2.5
standard install.
I'm not sure what verion of ksh it is - if you can tell me how to get a
version number (-v and --version do nothing) I can let you know.
>
> BTW, there is something I don't understand too well: you already sent
> some check.log, didn't you? But how did you manage to have it run
> properly last time? Or maybe I imagined you did.
I think you are confused with the output from the make that I got running by
butchering the config.status.
>
> Anyway, since it seems we have to go to safety, we will have to move
> to
>
> test ${FOO+set} = set || FOO=$foo
>
> Akim
I just tried you proposed change and I get a syntax error from:
test ${CONFIG_FILES+$config_files} = $config_files || CONFIG_FILES=$config_files
(I expect this is my mistake is not understanding what you are wanting)
trying as:
test ${CONFIG_FILES=$config_files} = $config_files || CONFIG_FILES=$config_files
Also fails returning just the last value again.
Next suggestion please :)
Regards
David
