From: Jonathan Larmour <jlarmour@redhat.com>
To: "Narayana, Venkat A." <NarayVA@nsc-msg01.network.com>
Cc: 'Gary Thomas' <gthomas@cambridge.redhat.com>,
ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Help! on building ecosconfigure
Date: Thu, 19 Apr 2001 12:35:00 -0000 [thread overview]
Message-ID: <3ADF3E04.D87FCF32@redhat.com> (raw)
In-Reply-To: <A7E1C26945C8D211ADBF0008C709661A02A487DF@nsc-msg02.network.com>
[ 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
next prev parent reply other threads:[~2001-04-19 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 14:32 Narayana, Venkat A.
2001-04-19 11:09 Narayana, Venkat A.
2001-04-19 11:47 ` Gary Thomas
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=3ADF3E04.D87FCF32@redhat.com \
--to=jlarmour@redhat.com \
--cc=NarayVA@nsc-msg01.network.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gthomas@cambridge.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).