[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[Libvir] Re: Add lots of warning flags to CFLAGS
- From: Jim Meyering <jim meyering net>
- To: "Richard W.M. Jones" <rjones redhat com>
- Cc: libvir-list <libvir-list redhat com>
- Subject: [Libvir] Re: Add lots of warning flags to CFLAGS
- Date: Thu, 01 Mar 2007 17:48:43 +0100
"Richard W.M. Jones" <rjones redhat com> wrote:
> Richard W.M. Jones wrote:
>> Mark McLoughlin wrote:
>>> On Thu, 2007-03-01 at 16:16 +0000, Daniel P. Berrange wrote:
>>>> On Thu, Mar 01, 2007 at 04:09:26PM +0000, Mark McLoughlin wrote:
>>>>> Uh, never mind this ... fixed patch attached.
>>>> Looks good to me, lets commit it.
>>>
>>> Done. Now, who wants to make it build with
>>> --enable-compile-warnings=error ? :-)
>> Actually that's a feature I _do_ want to use because the warnings
>> always fly past too quickly for me to read, so I will be testing it
>> out.
>
> Hmmm .... speaking too soon. rpcgen generates code stubs which do not
> pass -Wunused. I may look at whether we can do per-file flags,
Hi Rich,
Or make rpcgen mark the offending bits with __attribute__ ((__unused__))?
Or, postprocess the generated code to add the same?
> I think automake supports this.
You *can* do it in automake, but it's a kludge.
See the Per-Object Flags Emulation section of the manual.
"info automake per" should get it (hmm. but it doesn't work
on rawhide because the menu is missing).
http://sources.redhat.com/automake/automake.html#Per_002dObject-Flags
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]