public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ravi Kumar B S" <ravikbs@mindtree.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] problem building redboot - very strange
Date: Mon, 10 Sep 2001 11:24:00 -0000	[thread overview]
Message-ID: <2330401A6FE03445ADA682F5EBB7502D02B1813C@mtv01ex01.mindtree.com> (raw)

hi,

i am facing a problem in building redboot. the redbot is for ARM evaluator 7t
board and i am working on linux 7.1, kernel 2.4.2, gcc 2.95.2(arm-elf-gcc).
i did following things.

ecosconfig new e7t redboot
ecosconfig add flash
ecosconfig tree
make

i got the following error
arm-elf-gcc -mcpu=arm7tdmi -mno-short-load-words -Wl,--gc-sections
-Wl,-static -g -nostdlib
-L/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib -Ttarget.ld -o
/u/ARM/new-ecos/ecos/packages/redboot-work/install/bin/redboot.elf
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/version.o
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/extras.o: In function
`do_load':
/u/ARM/new-ecos/ecos/packages/redboot/current/src/load.c:337: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot/current/src/load.c:410: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/extras.o: In function
`fis_create':
/u/ARM/new-ecos/ecos/packages/redboot/current/src/flash.c:603: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/libtarget.a(io_flash_f
lash.o): In function `flash_errmsg':
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:417: undefined
reference to `flash_hwr_init'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:445: undefined
reference to `flash_erase_block'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:447: undefined
reference to `flash_hwr_map_error'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/libtarget.a(io_flash_f
lash.o): In function `flash_program':
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:274: undefined
reference to `flash_hwr_map_error'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:294: undefined
reference to `flash_program_buf'
collect2: ld returned 1 exit status
make[1]: ***
[/u/ARM/new-ecos/ecos/packages/redboot-work/install/bin/redboot.elf] Error 1
make[1]: Leaving directory
`/u/ARM/new-ecos/ecos/packages/redboot-work/redboot/current'
make: *** [build] Error 2

here are certain interesting results.
1. but if i see load.c file there is no occurence of flash_code_overlaps at
all.
2. i am able to build the redboot image if i dont add flash(i.e without
ecosconfig add flash). in this case the build goes fine.
3. but i am able to build redboot with flash support on a different machine
which is using the same tools.

can some body give some clue to fix this problem

regards,

ravi kumar





             reply	other threads:[~2001-09-10 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10 11:24 Ravi Kumar B S [this message]
2001-09-10 13:18 ` Jonathan Larmour
2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
2001-09-16 15:32   ` Gary Thomas
2001-09-17  2:15   ` Jesper Skov

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=2330401A6FE03445ADA682F5EBB7502D02B1813C@mtv01ex01.mindtree.com \
    --to=ravikbs@mindtree.com \
    --cc=ecos-discuss@sources.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).