Hi Nick,
I did run the configure script, and then saw the makefile.in but my
target name was not there in it.
Is there anything that I missed out to generate the makefile.in ?
Thanks,
Prashant
Nick Clifton wrote:
>
> Hi Prashant,
>
>> 2. Makefile.am- Added eelf32my_targe
Hi,
I created/modified the following files under ../binutils-2.19/ld :
1. Configure.tgt - Added support for my_target-*-elf*
2. Makefile.am- Added eelf32my_target.o under ALL_EMULATIONS and
eelf32my_target.c similar to what is done for CR16.
Hi all,
Now, I am able to generate header files for /binutils-2.19/bfd/ and
also, I am able to build libiberty, bfd, opcodes.
But now, while building binutils-2.19/binutils, I am getting the following
linker error even after modifying "Makefile.am" and "readelf.c" files in
/binutils-2.19/bi
Hi,
I am able to configure and build libiberty, bfd and opcodes after
adding new target details to the
corresponding configure script. But now, getting error while building
binutils-2.19/binutils/ as follows :
gcc -DHAVE_CONFIG_H -I. -I/root/binutils-2.19/binutils -I. -I.
-I/root/binutils
Hi Nick,
Thanks for the quick reply.
All the files which you mentioned are modified.
Also, I am referring the same document for which you have given a link.
But still I am getting the same error.
I have some doubt in the file "bfd/archures.c"
As mentioned in the link doc
I am trying to port binutils-2.19 to a new target.
I have modified all the require configuration files and make files to add
the new target details. I have also created .c and .h files in the
respective directories.
The configure script runs successfully and creates makefile.
But when I give 'm
