Re: Porting Binutils to A New Target And Getting Error.

2010-01-28 Thread Nick Clifton

Hi Prashant,


2. Makefile.am- Added eelf32my_target.o under ALL_EMULATIONS and
 eelf32my_target.c similar to what is done for CR16.


Did you regenerate Makefile.in after doing this ?

Cheers
  Nick




___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-28 Thread Prashant Purohit

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_target.o under ALL_EMULATIONS
 and
  eelf32my_target.c similar to what is done for CR16.
 
 Did you regenerate Makefile.in after doing this ?
 
 Cheers
Nick
 
 
 
 
 ___
 bug-binutils mailing list
 bug-binutils@gnu.org
 http://lists.gnu.org/mailman/listinfo/bug-binutils
 
 

-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27366927.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-27 Thread Prashant Purohit

 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.

   3. emulparams/elf32my_target.sh - similar to CR16
   4. emultempl/my_targetelf.em- similar to CR16
   5. scripttempl/elf32tel_arm9.sc - similar to CR16


Still getting the same error while building.

gcc: eelf32my_target.o: No such file or directory

Thanks  Regards,
Prashant.



-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27334472.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-21 Thread Prashant Purohit

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/binutils/ for the new target :

.
.
../bfd/.libs/libbfd.a(targets.o):(.data+0x4): undefined reference to
`bfd_elf32_my_target_vec'
../bfd/.libs/libbfd.a(targets.o):(.rodata+0x8): undefined reference to
`bfd_elf32_my_target_vec'
../bfd/.libs/libbfd.a(targets.o):(.rodata+0x20): undefined reference to
`bfd_elf32_my_target_vec'
collect2: ld returned 1 exit status
make[2]: *** [size] Error 1
make[2]: Leaving directory `/root/temp/binutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/temp/binutils'
make: *** [all] Error 2

Thanks  Regards,
Prashant
-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27253395.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-13 Thread Prashant Purohit


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-2.19/binutils -I../bfd
-I/root/binutils-2.19/binutils/../bfd
-I/root/binutils-2.19/binutils/../include
-DLOCALEDIR=\/root/temp_install//share/locale\
-Dbin_dummy_emulation=bin_vanilla_emulation   -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Werror -g -O2 -c /root/binutils-2.19/binutils/size.c

In file included from /root/binutils-2.19/binutils/sysdep.h:25, 
 from /root/binutils-2.19/binutils/size.c:33: 
./config.h:192:16: error: missing terminating  character


In config.h file the target name is getting generated as :

/* Configured target name. */ 
#define TARGET mytarget-unknown

-elf

Which is the cause of the error.  I would like to know which file generates
config.h.

Thanks  Regards,
Prashant
-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27141973.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-08 Thread Prashant Purohit

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 document, I have added new target name to
bfd_architecture enumeration  in the bfd/archures.c but this portion of
the code is commented in the source code.

   Whether I need to un-comment that portion or need to run some other
utility before running configure script and make utility.

   Thanks in advance,

Regards,
Prashant







Nick Clifton wrote:
 
 Hi Prashant,
 
 I am trying to port binutils-2.19 to a new target.
 
 Note - you would be better off using the current mainline development 
 sources.
 
 But when I give 'make all' command, I am getting 'unknown target vector'
 error.
 
 Look at the bfd/config.bfd file.  You will need to add an entry for your 
 target.
 
 If you have not done so already then you will also need to modify the 
 bfd/archures.c and bfd/targets.c files as well.
 
 Cheers
Nick
 
 PS.  There is now a guide to porting the binutils to a new target, which 
 you may find helpful.  See:
 
http://sourceware.org/binutils/binutils-porting-guide.txt
 
 
 
 ___
 bug-binutils mailing list
 bug-binutils@gnu.org
 http://lists.gnu.org/mailman/listinfo/bug-binutils
 
 

-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27073520.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Porting Binutils to A New Target And Getting Error.

2010-01-07 Thread Prashant Purohit

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 'make all' command, I am getting 'unknown target vector'
error.

The log looks like:

.
.
.
.
looking for a compliant stdint.h in stdint.h, checking for uintmax_t... yes
checking for uintptr_t... yes
checking for int_least32_t... yes
checking for int_fast32_t... yes
checking for uint64_t... yes
checking what to include in bfd_stdint.h... stdint.h (already complete)
checking whether time.h and sys/time.h may both be included... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking whether string.h and strings.h may both be included... yes
checking for fcntl... yes
checking for getpagesize... yes
checking for setitimer... yes
checking for sysconf... yes
checking for fdopen... yes
checking for getuid... yes
checking for getgid... yes
checking for strtoull... yes
checking whether basename is declared... yes
checking whether ftello is declared... yes
checking whether ftello64 is declared... yes
checking whether fseeko is declared... yes
checking whether fseeko64 is declared... yes
checking whether ffs is declared... yes
checking whether free is declared... yes
checking whether getenv is declared... yes
checking whether malloc is declared... yes
checking whether realloc is declared... yes
checking whether stpcpy is declared... yes
checking whether strstr is declared... yes
checking whether snprintf is declared... yes
checking whether vsnprintf is declared... yes
checking for library containing zlibVersion... -lz
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
configure: error: *** unknown target vector bfd_elf32_my_target_vec
.
.
.

Help me in fixing this problem.

Thanks in advance. 
-- 
View this message in context: 
http://old.nabble.com/Porting-Binutils-to-A-New-Target-And-Getting-Error.-tp27058018p27058018.html
Sent from the Gnu - Binutils - Bugs mailing list archive at Nabble.com.



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils


Re: Porting Binutils to A New Target And Getting Error.

2010-01-07 Thread Nick Clifton

Hi Prashant,


I am trying to port binutils-2.19 to a new target.


Note - you would be better off using the current mainline development 
sources.



But when I give 'make all' command, I am getting 'unknown target vector'
error.


Look at the bfd/config.bfd file.  You will need to add an entry for your 
target.


If you have not done so already then you will also need to modify the 
bfd/archures.c and bfd/targets.c files as well.


Cheers
  Nick

PS.  There is now a guide to porting the binutils to a new target, which 
you may find helpful.  See:


  http://sourceware.org/binutils/binutils-porting-guide.txt



___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils