RE: [ECOS] Help! on building ecosconfigure

RE: [ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

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
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

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

"Narayana, Venkat A." wrote:
> 
> 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
> Supported emulations: armelf_linux armelf_linux26 armelf

You are using arm-linux binutils. Instead gcc should be compiled to use 
generic arm-elf or xscale-elf tools. ARM linux tools are uesd to compile
linux programs.

Get binutils sources from http://sources.redhat.com/binutils/

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

RE: [ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

Thanks Mark, this -fno-builtin solution worked.
But there's a slight change in the way i did it.
Made these changes in redboot_ROM.ecm file, because i am
importing it.

Thanks and Regards for ALL
Venkat



-----Original Message-----
From: Mark Salter [ mailto:msalter@redhat.com ]
Sent: Thursday, April 19, 2001 2:43 PM
To: NarayVA@nsc-msg01.network.com
Cc: gthomas@cambridge.redhat.com; ecos-discuss@sourceware.cygnus.com;
ecos-discuss@sourceware.cygnus.com; jlarmour@redhat.com
Subject: Re: [ECOS] Help! on building ecosconfigure


>>>>> Narayana, Venkat A writes:

> 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___


Hmm, I saw this on another architecture that uses a recent gcc.
The problem is with gcc builtins. Gcc "optimizes" things like:

  printf("foo") ==> puts("foo")

and

  printf("\n") ==> putchar('\n')


Of course, RedBoot doesn't provide putchar or puts, so you get link
errors. Try this patch which adds -fno-builtin to the compile line.

--Mark


Index: hal_arm_iq80310.cdl
===================================================================
RCS file:
/home/cvs/ecc/ecc/hal/arm/iq80310/current/cdl/hal_arm_iq80310.cdl,v
retrieving revision 1.14
diff -u -p -5 -c -r1.14 hal_arm_iq80310.cdl
cvs server: conflicting specifications of output style
*** hal_arm_iq80310.cdl	2001/04/17 14:42:58	1.14
--- hal_arm_iq80310.cdl	2001/04/19 19:35:59
*************** cdl_package CYGPKG_HAL_ARM_IQ80310 {
*** 192,202 ****
  
          cdl_option CYGBLD_GLOBAL_CFLAGS {
              display "Global compiler flags"
              flavor  data
              no_define
!             default_value { "-Wall -Wpointer-arith -Wstrict-prototypes
-Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections
-fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority
-mapcs-frame" }
              description   "
                  This option controls the global compiler flags which are
used to
                  compile all packages by default. Individual packages may
define
                  options which override these global flags."
          }
--- 192,202 ----
  
          cdl_option CYGBLD_GLOBAL_CFLAGS {
              display "Global compiler flags"
              flavor  data
              no_define
!             default_value { "-fno-builtin -Wall -Wpointer-arith
-Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc
-finit-priority -mapcs-frame" }
              description   "
                  This option controls the global compiler flags which are
used to
                  compile all packages by default. Individual packages may
define
                  options which override these global flags."
          }

Re: [ECOS] Help! on building ecosconfigure

[Lewin A.R.W. Edwards]

> > printf("thing%s","")
>
>Yes, but that is a workaround in the same way as -fno-builtin is a
>workaround. Just a workaround, not a fix.

Yes, but it is a workaround that anybody can use now without waiting for 
patches, and which avoids the problem you mention of disabling "benevolent" 
optimizations.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"... a man who is endowed with real qualities of leadership will be tempted 
to refrain from taking part in political life; because [...] the situation 
does not call for a man who has a capacity for constructive statesmanship 
but rather for a man who is capable of bargaining for the favour of the 
majority. Thus the situation will appeal to small minds and will attract 
them accordingly."

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

"Lewin A.R.W. Edwards" wrote:
> 
> >useful builtins that we do want. RedBoot's *printf routines and gets() etc.
> >will have to be renamed. Actually the *printf() routines should be merged
> >into the standard diag_ routines and those used in preference.
> 
> Can't you just work around it by changing
> 
> printf("thing")
> 
> to
> 
> printf("thing%s","")
> or
> printf("%s","thing")

Yes, but that is a workaround in the same way as -fno-builtin is a
workaround. Just a workaround, not a fix.

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

Re: [ECOS] Help! on building ecosconfigure

[Lewin A.R.W. Edwards]

>useful builtins that we do want. RedBoot's *printf routines and gets() etc.
>will have to be renamed. Actually the *printf() routines should be merged
>into the standard diag_ routines and those used in preference.

Can't you just work around it by changing

printf("thing")

to

printf("thing%s","")
or
printf("%s","thing")

?

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"... a man who is endowed with real qualities of leadership will be tempted 
to refrain from taking part in political life; because [...] the situation 
does not call for a man who has a capacity for constructive statesmanship 
but rather for a man who is capable of bargaining for the favour of the 
majority. Thus the situation will appeal to small minds and will attract 
them accordingly."

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

Mark Salter wrote:
> 
> >>>>> Narayana, Venkat A writes:
> 
> > 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___
> 
> Hmm, I saw this on another architecture that uses a recent gcc.
> The problem is with gcc builtins. Gcc "optimizes" things like:
> 
>   printf("foo") ==> puts("foo")
> 
> and
> 
>   printf("\n") ==> putchar('\n')
> 
> Of course, RedBoot doesn't provide putchar or puts, so you get link
> errors. Try this patch which adds -fno-builtin to the compile line.

Bugger. That's a problem with RedBoot using ISO C standard names without a
full ISO C compatible environment (or for that matter without an ISO C
implementation). I never liked the overloading of the usage, or the
inevitable result that some parts use RedBoot's printf, some part's use
diag_printf, leading to code duplication.

-fno-builtin is not an acceptable solution as it turns off a bunch of
useful builtins that we do want. RedBoot's *printf routines and gets() etc.
will have to be renamed. Actually the *printf() routines should be merged
into the standard diag_ routines and those used in preference.

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

Re: [ECOS] Help! on building ecosconfigure

[Mark Salter]

>>>>> Narayana, Venkat A writes:

> 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___


Hmm, I saw this on another architecture that uses a recent gcc.
The problem is with gcc builtins. Gcc "optimizes" things like:

  printf("foo") ==> puts("foo")

and

  printf("\n") ==> putchar('\n')


Of course, RedBoot doesn't provide putchar or puts, so you get link
errors. Try this patch which adds -fno-builtin to the compile line.

--Mark


Index: hal_arm_iq80310.cdl
===================================================================
RCS file: /home/cvs/ecc/ecc/hal/arm/iq80310/current/cdl/hal_arm_iq80310.cdl,v
retrieving revision 1.14
diff -u -p -5 -c -r1.14 hal_arm_iq80310.cdl
cvs server: conflicting specifications of output style
*** hal_arm_iq80310.cdl	2001/04/17 14:42:58	1.14
--- hal_arm_iq80310.cdl	2001/04/19 19:35:59
*************** cdl_package CYGPKG_HAL_ARM_IQ80310 {
*** 192,202 ****
  
          cdl_option CYGBLD_GLOBAL_CFLAGS {
              display "Global compiler flags"
              flavor  data
              no_define
!             default_value { "-Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -mapcs-frame" }
              description   "
                  This option controls the global compiler flags which are used to
                  compile all packages by default. Individual packages may define
                  options which override these global flags."
          }
--- 192,202 ----
  
          cdl_option CYGBLD_GLOBAL_CFLAGS {
              display "Global compiler flags"
              flavor  data
              no_define
!             default_value { "-fno-builtin -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -mapcs-frame" }
              description   "
                  This option controls the global compiler flags which are used to
                  compile all packages by default. Individual packages may define
                  options which override these global flags."
          }

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

Gary Thomas wrote:
> 
> 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.

I thought that apps built with arm-elf tools would still work though? They
just wouldn't be optimised for xscale.
 
> > 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.

Oh he was trying to build eCos programs. In that case the problem is bound
to be that he is reusing the same build tree and configuration and just
expecting it to work.

In that case what Venkat needs to do is start over *in a new build
directory*. Including rerunning "ecosconfig new iq80310" or whatever it is
he wants to do now, and then editting the ecos.ecc to change
CYG_HAL_STARTUP to have a user_value of ROM.

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

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

[ Please trim unnecessary quoted text in future. ]

"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.

You did this yourself I presume.

> So, i changed xscale-elf-gcc =>
> arm-elf-gcc
> 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.
> 
[snip 
> 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.

I thought the whole point before was that you couldn't build anything when
you had linked the xscale-elf tools to arm-linux tools.

> ___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'

It looks to me like more changed than just a make clean - I tried what you
did here for the iq80310 target (which I assume is what you are using, but
you don't say) and it worked fine.

You can get to a more consistent state by deleting _everything_ in your
build directory, including your entire install tree with the exception of
the .ecc file.

Then rerun "ecosconfig tree" and then "make".

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

RE: [ECOS] Help! on building ecosconfigure

[Gary Thomas]

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

RE: [ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

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
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___




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

RE: [ECOS] Help! on building ecosconfigure

[Gary Thomas]

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

RE: [ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

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'?

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
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

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

"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

RE: [ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

Hi,
I can do that,but it takes away the fun;-).
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.

Venkat


"Narayana, Venkat A." wrote:
> 
> Hi all,
> I have downloaded the ecos sources from cvs/redhat site.
> In the 'host' directory, i followed README and ran ' configure script'.
> What values i should give for 'build, host and target'?

The host directory is only relevant if you are building the host tools,
like ecosconfig. But you can download prebuilts for Windows and Linux from
http://sources.redhat.com/ecos/anoncvs.html

> I want to make
> redboot for RAM startup
> for XScale arch. what documents are relevant ?

The RedBoot user's guide. Go to http://sources.redhat.com/redboot/

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

Re: [ECOS] Help! on building ecosconfigure

[Jonathan Larmour]

"Narayana, Venkat A." wrote:
> 
> Hi all,
> I have downloaded the ecos sources from cvs/redhat site.
> In the 'host' directory, i followed README and ran ' configure script'.
> What values i should give for 'build, host and target'?

The host directory is only relevant if you are building the host tools,
like ecosconfig. But you can download prebuilts for Windows and Linux from
http://sources.redhat.com/ecos/anoncvs.html

> I want to make
> redboot for RAM startup
> for XScale arch. what documents are relevant ?

The RedBoot user's guide. Go to http://sources.redhat.com/redboot/

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

[ECOS] Help! on building ecosconfigure

[Narayana, Venkat A.]

Hi all,
I have downloaded the ecos sources from cvs/redhat site.
In the 'host' directory, i followed README and ran ' configure script'.
What values i should give for 'build, host and target'? I want to make
redboot for RAM startup
for XScale arch. what documents are relevant ? 

Thanks in advance,
Regards,
Venkat N