[ovs-dev] [PATCH 3/3] command-line: add ovs_cmdl_context
Russell Bryant
rbryant at redhat.com
Tue Mar 17 15:57:06 UTC 2015
On 03/17/2015 11:49 AM, Ben Pfaff wrote:
> On Tue, Mar 17, 2015 at 11:31:17AM -0400, Russell Bryant wrote:
>> On 03/17/2015 11:11 AM, Ben Pfaff wrote:
>> With just -Werror, I get:
>>
>> libtool: compile: clang -DHAVE_CONFIG_H -I. -I ./include -I ./include
>> -I ./lib -I ./lib -Wstrict-prototypes -Wall -Wextra -Wno-sign-compare
>> -Wpointer-arith -Wformat-security -Wno-format-zero-length -Wswitch-enum
>> -Wunused-parameter -Wbad-function-cast -Wcast-align -Wstrict-prototypes
>> -Wold-style-definition -Wmissing-prototypes -Wmissing-field-initializers
>> -Wthread-safety -fno-strict-aliasing -Werror -MT lib/aes128.lo -MD -MP
>> -MF lib/.deps/aes128.Tpo -c lib/aes128.c -o lib/aes128.o
>> clang: error: argument unused during compilation: '-I .'
>> clang: error: argument unused during compilation: '-I ./include'
>> clang: error: argument unused during compilation: '-I ./include'
>> clang: error: argument unused during compilation: '-I ./lib'
>> clang: error: argument unused during compilation: '-I ./lib'
>> Makefile:3454: recipe for target 'lib/aes128.lo' failed
>
> It's bizarre to report -I options as "argument[s] unused during
> compilation" so I typed this into Google and found
> https://github.com/perl11/potion/issues/41, which says (in part):
>
> It's because ccache is not yet fully clang-compatible, and it
> produces this warning, ...
>
> Any chance that ccache is enabled and interfering somehow with the clang
> build? Maybe it should be disabled for clang.
>
Good find! Yes, that's it.
$ which clang
/usr/lib64/ccache/clang
Removing the ccache symlink for clang makes it so I get the same result
as you.
--
Russell Bryant
More information about the dev
mailing list