Re: The meaning of -Wall

["nelson"<yunakaof at usp dot br>]

Hi,

I am only a only a spectator in list, watching the list
for notices for the gcc 3.3 tarball to compile it in a
Tru64 (v5.1b) OS. ( Alpha platform )

I have to compile some GNU programs, in above mentioned
OS, and in one of them I have a problem with this flag ( -Wall )
I have to remove this and one more  ( I dont remember now what
the flag ) manually from all makefiles of the distribution directory
after the "sh ./configure" to have a sucessfull compilation.

Tru64 comes with built-in cc ad ld, and the ld dont recognize
this flags.

If your propose will solve this type of problems I think it is good.

( gnu ld is one of softwares that dont compiles in this OS/platform ).

bye

( Sorry for intrusion ... , )


At 17:24 03/05/03 -0700, you wrote:
> "Joseph S. Myers" wrote:
>
> > With all the ways available of configuring and rewriting options,
>
> [albeit ugly ways ;-]
>
> > I think the value of a configuration file ... for FSF GCC is negative
>
> OK.  We'll always disagree on that.  If the available ways for doing
> something are ugly, then it's worth making life easier.
>
> > IDEs however might well have such a configuration file of their own.
> > What would be useful in FSF GCC is pragmas for fine-grained warning
> > control within source files.
>
> Still and all, if you're going to add such pragmas, it should be
> made a trivial mapping:
>
>   #pragma gcc_option  Wall
>   #pragma gcc_option  no-warn-unused-static
>
> and if I choose to use it in some other way:
>
>   #pragma gcc_option  I /path/to/proj/headers
>
> let it fail only because it is too difficult to be handled,
> and not because the code cannot understand the request
> or because the code believes I shouldn't want to make
> such a request.