This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem compiling 2.17 with GCC 4.1.1

"George R. Kasica" wrote:

> gcc -DHAVE_CONFIG_H -I. -I.././opcodes -I. -D_GNU_SOURCE -I.
> -I.././opcodes -I../bfd -I.././opcodes/../include
> -I.././opcodes/../bfd -I.././opcodes/../intl -I../intl -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c i386-dis.c
> -o i386-dis.o
> cc1: warnings being treated as errors
> i386-dis.c: In function 'print_operand_value':
> i386-dis.c:3228: warning: value computed is not used
> i386-dis.c: In function 'VMX_Fixup':
> i386-dis.c:4761: warning: value computed is not used
> i386-dis.c:4764: warning: value computed is not used

Those are just harmless (?) warnings but because -Werror was supplied to
gcc they are turned into errors.  You should run configure with
--disable-werror and everything should be fine.

Ideally, the point of having -Werror turned on by default is to keep the
build clean, i.e. make sure that any warnings are addressed instead of
ignored, but it seems like you must have stumbled upon a combination of
platform and compiler that slipped through the cracks of testing.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]