This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
protoize.c: recently introduced syntax error
Donn Terry writes:
> In your recent change to protoize.c, there seems to be a missing operator
> between the calls to S_ISDIR and access (on the next line) causing a complaint
> about a object which is not a function being called.
You are quite right; God alone knows how I missed it. (Now that I
recompile protoize.c, this is indeed complained about. I shall have to
redirect stderr to the loudspeakers, or something; it appears I miss the
glaringly obvious otherwise.)
> (You don't want to know why I can't cut-and-paste in the exact context, or
> I would.)
Here's a patch (not that I really expect it'll be needed; this change is
not rocket science to fix).
2000-08-22 Nix <nix@esperi.demon.co.uk>
* protoize.c (munge_compile_params): Correct typo.
--- egcs/gcc/protoize.c Tue Aug 22 21:16:05 2000
+++ egcs-hacking/gcc/protoize.c Tue Aug 22 21:16:26 2000
@@ -2001,7 +2001,7 @@ munge_compile_params (params_list)
temp_params[param_count++] = "-o";
if ((stat (HOST_BIT_BUCKET, &st) == 0) && (!S_ISDIR (st.st_mode))
- (access (HOST_BIT_BUCKET, W_OK) == 0))
+ && (access (HOST_BIT_BUCKET, W_OK) == 0))
temp_params[param_count++] = HOST_BIT_BUCKET;
else
/* FIXME: This is hardly likely to be right, if HOST_BIT_BUCKET is not
--
`OS's and GUI's come and go, only Emacs has lasting power.' --- Per Abrahamsen