This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: How to test binutils?
- From: Nick Clifton <nickc at redhat dot com>
- To: Houda Benabderrazik <hbena76 at yahoo dot fr>
- Cc: binutils at sources dot redhat dot com
- Date: Wed, 05 May 2004 17:02:43 +0100
- Subject: Re: How to test binutils?
- References: <20040430094030.12953.qmail@web60401.mail.yahoo.com>
Hi Houda,
Does anyone know how to build Gas and binutils after
adding new processor (tc-cpu.c tc-cpu.h)?
You will probably need to add more files than these. In particular you
will probably need to create these files:
bfd/cpu-<name>.c
bfd/elf32-<name>.c [I am assuming that you are using the ELF file
format]
opcodes/<name>-dis.c
opcodes/<name>-asm.c
You will also need to add entries to the gas/configure.in,
bfd/config.bfd, ld/configure.tgt, opcodes/configure.in and
opcodes/disassembler.c files, as well as regenerating the various
*/configure files and adding an entry to the top level config.sub file.
As for building GAS and binutils you should try to follow the standard
procedure for building a cross-targeted toolchain. ie create a separate
build directory that is not part of the sources directories. In that
directory run the "configure" script from the top level of the sources
directory and give it a command line switch of "--target=<name>-elf".
If this succeeds then run "make". If that passes then run "make check".
How can i test what the program in Mac OS X?
I am not quite sure what you mean here. If you want to test to see if
your new code works then the above procedure should be a good start.
Cheers
Nick