This is the mail archive of the binutils@sourceware.org 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] |
On Fri, 2005-10-14 at 05:39, Doug Evans wrote: > gcc -DHAVE_CONFIG_H -I. -I/home/dje/gnu/src/opcodes -I. -D_GNU_SOURCE -I. -I/home/dje/gnu/src/opcodes -I../bfd -I/home/dje/gnu/src/opcodes/../include -I/home/dje/gnu/src/opcodes/../bfd -I/home/dje/gnu/src/opcodes/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c /home/dje/gnu/src/opcodes/ia64-gen.c > /home/dje/gnu/src/opcodes/ia64-gen.c: In function `print_main_table': > /home/dje/gnu/src/opcodes/ia64-gen.c:2704: warning: long unsigned int format, different type arg (arg 3) > /home/dje/gnu/src/opcodes/ia64-gen.c:2706: warning: long unsigned int format, different type arg (arg 3) ia64-gen.c requires the 64-bit (BFD64) definition of fprintf_vma from bfd/bfd-in2.h. We could perhaps just copy the 32-bit host version of that into the ia64-gen.c file and rename it. It is only 4 lines of code, and will work for both 32-bit and 64-bit hosts. An alternative is to require --enable-64-bit-bfd in order to build it. This is what is done in the bfd directory, where the ia64 files are in BFD64_BACKENDS, and are only built if BFD64 is defined. This would require more hackery than the above, as there is currently no distinction between 32-bit and 64-bit targets in the opcodes directory. How about the attached patch? -- Jim Wilson, GNU Tools Support, http://www.specifix.com
Attachment:
patch.32-bit.ia64-gen
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |