From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas To: "Narayana, Venkat A." Cc: Jonathan Larmour , ecos-discuss@sourceware.cygnus.com Subject: RE: [ECOS] Help! on building ecosconfigure Date: Thu, 19 Apr 2001 12:33:00 -0000 Message-id: References: X-SW-Source: 2001-04/msg00215.html On 19-Apr-2001 Narayana, Venkat A. wrote: > Hi, > Thanks for the reply.After you have pointed out, that my 'ld' is from > arm-linux, instead of arm-elf/xscale-elf,i looked at my tools/biin and > realised > that xscale-elf-gcc => arm-linux-gcc. So, i changed xscale-elf-gcc => > arm-elf-gcc Note: arm-elf-XXX is not xscale-elf-XXX. There are differences in the toolchains, certainly those required to support the Xscale (aka StrongARM-2) architecture. > and did a 'make' in my redboot.ROM directory, to build ROM startup files. > Guess what!!! It built the binaries!. BUT, after i did 'make clean' and then > did > 'make'( i want ot build ROM Startup bin files),now, i got a whole bunch of > new > errors like below. > > To answer your query on what i used to configure: > host=i686-pc-linux > target=arm-elf > prefix = /home/users/ecoscvs/tools > > The following info may be usefule for you; > xscale-elf-gcc --version = 3.0 > xscale-elf-gcc -dumpmachine = arm-elf > gcc --version = 3.0 > gcc -dumpmachine = i686-pc-linux-gnu > > Why am i getting these new errors/ does my path is bad? > And why did in the mixed up case of gcc and ld, binaries got built. > > ___Start____ > redboot_net_io.o(.text+0xa00): undefined reference to `puts' > redboot_net_io.o(.text+0xa4c): undefined reference to `puts' > /home/users/redboot.ROM/install/lib/libtarget.a(io_flash_flash.o): In > function `flash_erase': > io_flash_flash.o(.text+0x2c8): undefined reference to `putchar' > io_flash_flash.o(.text+0x2e0): undefined reference to `putchar' > /home/users/redboot.ROM/install/lib/libtarget.a(io_flash_flash.o): In > function `flash_program' > ___End___ > I've no clue about these - those functions are not used in normal eCos programs at all. Maybe you could send me one of these files (reboot_net_io.o - *NOT* to the list) I'll give it a glance. > > > > On 19-Apr-2001 Narayana, Venkat A. wrote: >> Hi, >> I have cross-compiled gcc/ld/nm/objcopy/ar/as for 'arm-elf'( i already > have >> these for 'arm-linux'). And, after that, when i tried to compile redboot > for >> ROM startup( in accordance with page23 of Redboot User's guide), i am > still >> getting this error. >> Is 'xscale-elf' a different format? Can't i use 'arm-elf' or 'arm-linux' > in >> lieu >> of 'xscale-elf'? >> > > They are basically the same, but slightly different configurations. > >>From the messages below, it does not look like 'xscale-elf-gcc' is calling > the appropriate 'xscale-elf-ld' file. When you built these, what > "configure" > line did you use? In particular, what were the values for --prefix and > --host-prefix? > >> Your help is greatly appreciated. >> >> Venkat N >> >> -----Original Message----- >> From: Narayana, Venkat A. [ mailto:NarayVA@nsc-msg01.network.com ] >> Sent: Wednesday, April 18, 2001 1:20 PM >> To: 'Jonathan Larmour' >> Cc: 'ecos-discuss@sourceware.cygnus.com' >> Subject: RE: [ECOS] Help! on building ecosconfigure >> >> >> Hi, >> I compiled ecosconfig, and tried to build redboot for ROM startup, >> whence i got these errors: >> What is that i am doing wrong? >> >> _START_LOG__ >> xscale-elf-gcc -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef >> -Woverloaded-virtual -g -O2 -fno-rtti -fno-exceptions -fvtable-gc >> -finit-priority -mapcs-frame -nostdlib -Wl,-r,--whole-archive -o >> /home/users/redboot.ROM/install/lib/extras.o >> /home/users/redboot.ROM/install/lib/libextras.a >> /usr/arm/tools/arm-linux/bin/ld: unrecognised emulation mode: elf32arm > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This should be the xscale-elf version, not any arm-linux one. > >> Supported emulations: armelf_linux armelf_linux26 armelf >> collect2: ld returned 1 exit status >> make[1]: *** [/home/users/redboot.ROM/install/lib/extras.o] Error 1 >> make[1]: Leaving directory `/home/users/redboot.ROM/hal/common/current' >> make: *** [build] Error 2 >> [root@narayva-nt redboot.ROM]# uname -a >> Linux narayva-nt.network.com 2.2.5-15 #14 Wed Mar 28 10:02:40 CST 2001 > i686 >> unknown >> _END_LOG___ >> >> >> -----Original Message----- >> From: Jonathan Larmour [ mailto:jlarmour@redhat.com ] >> Sent: Wednesday, April 18, 2001 12:56 PM >> To: Narayana, Venkat A. >> Cc: 'ecos-discuss@sourceware.cygnus.com' >> Subject: Re: [ECOS] Help! on building ecosconfigure >> >> >> "Narayana, Venkat A." wrote: >>> Moreover, i think that ecosconfig tool has something to do with >>> cross-compilation.I reasoned that on the basis of input parameters >>> that we pass to configure script.I went thru the 'ecos Getting started' >>> manual and Redboot User's guide, but i didn't find any examples of making >>> ecosconfigure tool. >>> So, if i need to build Redboot ROM startup for ARM arch, then, since i > use >>> ecosconfig tool( page 23 of Redboot users guide), then shouldn't i > compile >>> ecosconfig to take care of cross-compilation? i guessing here. >> >> No, ecosconfig is purely a host-side tool. It has no knowledge of >> particular targets. Using the prebuilt ones built for Linux and Windows, > if >> one of those is your host, should be fine. >> >> Jifl >> -- >> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062 >> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine