public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Building RedBoot for SH3 targets with new toolchain
Date: Wed, 21 Jan 2009 19:48:00 -0000	[thread overview]
Message-ID: <49777C14.8070201@dallaway.org.uk> (raw)

Hi Jifl

There is a problem linking RedBoot for all SH3 targets with the new
sh-elf toolchain based on GCC 4.3.2. For example, linking RAM RedBoot
for sh7708:

> /var/local/releng/build/redboot/install/lib/extras.o: In function `fis_write':
> /var/local/releng/ecos-3.0pre/packages/redboot/current/src/flash.c:1660: undefined reference to `___udivsi3_i4i'
> /var/local/releng/build/redboot/install/lib/extras.o: In function `fis_erase':
> /var/local/releng/ecos-3.0pre/packages/redboot/current/src/flash.c:1710: undefined reference to `___udivsi3_i4i'
> /var/local/releng/build/redboot/install/lib/extras.o: In function `do_flash_init':
> /var/local/releng/ecos-3.0pre/packages/redboot/current/src/flash.c:1920: undefined reference to `___udivsi3_i4i'
> /var/local/releng/build/redboot/install/lib/extras.o: In function `fis_create':
> /var/local/releng/ecos-3.0pre/packages/redboot/current/src/flash.c:1286: undefined reference to `___udivsi3_i4i'
> /var/local/releng/build/redboot/install/lib/libtarget.a(hal_common_hal_if.o): In function `flash_fis_op2':
> /var/local/releng/ecos-3.0pre/packages/hal/common/current/src/hal_if.c:264: undefined reference to `___udivsi3_i4i'
> /var/local/releng/build/redboot/install/lib/libtarget.a(io_flash_flash.o):/var/local/releng/ecos-3.0pre/packages/io/flash/current/src/flash.c:595: more undefined references to `___udivsi3_i4i' follow
> collect2: ld returned 1 exit status

I note that the multi-libbing for sh-elf has changed, but for both old
and new toolchains:

> [jld@cog ~]$ sh-elf-gcc -m3 -print-multi-directory
> m2
> [jld@cog ~]$ sh-elf-gcc -m3 -ml -print-multi-directory
> ml/m2
> [jld@cog ~]$

The m2 and ml/m2 multi-libs exist in both toolchains.

Building RedBoot for target sh4_202_md (an SH4 target) works fine with
the new tools and building RedBoot for SH3 targets works fine with the
old tools.

Any idea what's going wrong here?

John Dallaway

             reply	other threads:[~2009-01-21 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 19:48 John Dallaway [this message]
2009-01-21 20:30 ` Jonathan Larmour
2009-01-21 22:08   ` John Dallaway
2009-01-21 22:33     ` Jonathan Larmour
2009-01-21 23:34       ` John Dallaway
2009-01-22  0:29         ` Jonathan Larmour
2009-01-22 10:15           ` John Dallaway
2009-01-22 10:31             ` Andrew Lunn
2009-01-22 12:30               ` John Dallaway
2009-01-22 14:40                 ` Bart Veer
2009-01-22 16:59                   ` John Dallaway

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=49777C14.8070201@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@eCosCentric.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).