public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: "Narayana, Venkat A." <NarayVA@nsc-msg01.network.com>
Cc: "ecos-discuss@sourceware.cygnus.com"
	<ecos-discuss@sourceware.cygnus.com>,
	Jonathan Larmour <jlarmour@redhat.com>
Subject: RE: [ECOS] Help! on building ecosconfigure
Date: Thu, 19 Apr 2001 11:47:00 -0000	[thread overview]
Message-ID: <XFMail.20010419124648.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <A7E1C26945C8D211ADBF0008C709661A02A487DE@nsc-msg02.network.com>

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

  reply	other threads:[~2001-04-19 11:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 11:09 Narayana, Venkat A.
2001-04-19 11:47 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 14:32 Narayana, Venkat A.
2001-04-19 12:16 Narayana, Venkat A.
2001-04-19 12:33 ` Gary Thomas
2001-04-19 12:39   ` Jonathan Larmour
2001-04-19 12:35 ` Jonathan Larmour
2001-04-19 12:40 ` Mark Salter
2001-04-19 12:51   ` Jonathan Larmour
2001-04-19 13:03     ` Lewin A.R.W. Edwards
2001-04-19 13:56       ` Jonathan Larmour
2001-04-19 14:04         ` Lewin A.R.W. Edwards
2001-04-18 11:18 Narayana, Venkat A.
2001-04-18 11:30 ` Jonathan Larmour
2001-04-18 10:48 Narayana, Venkat A.
2001-04-18 10:56 ` Jonathan Larmour
2001-04-18 10:27 Narayana, Venkat A.
2001-04-18 10:32 ` Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XFMail.20010419124648.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=NarayVA@nsc-msg01.network.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).