trap 0 vs. gcc's configure

[Egmont Koblinger]

Hi,

In bash 3.0 manually executing the command `` trap 0 '' goes fine. Also,
putting it in a small script is fine, too.

However, if I try to compile gcc 3.3.4, when it tries to execute the
`` trap 0 '' command at the end of its outermost configure script, it
prints this:
trap: usage: trap [-lp] [[arg] signal_spec ...]
and this trap command exits with an error.

Adding a ``-x'' to the interpreter line of this configure scripts yields
to this:

[...]
creating ./config.status
creating Makefile
creating install-defs.sh
creating config.h
+ true
+ cd /tmp/object
+ rm -rf /tmp/cNf12649
+ trap 0
trap: usage: trap [-lp] [[arg] signal_spec ...]
+ rm -rf Makefile.tem /tmp/cNf12649
+ exit 1


Strange...

bash-2.05b had no trouble.

If I change this `` trap 0 '' to `` trap - 0 '' then it's okay.

Is it a bug in bash, or maybe gcc's configure sets some variables which
influence the behavior of trap? I haven't found such circumstances (e.g.
posixly_correct or stuff like that) in 'help bash' and 'man bash'.



-- 
Egmont