From: John Dallaway <john@dallaway.org.uk>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Building RedBoot for SH3 targets with new toolchain
Date: Wed, 21 Jan 2009 23:34:00 -0000 [thread overview]
Message-ID: <4977B0E2.3040806@dallaway.org.uk> (raw)
In-Reply-To: <4977A2A8.1030608@eCosCentric.com>
Hi Jifl
Jonathan Larmour wrote:
> Anyway, linux build now uploaded to
> ftp://ecos.sourceware.org/pub/ecos/gnutools/ecoscentric-gnutools-sh-elf-20090121-sw.i386linux.tar.bz2
>
> If that looks ok, I'll try and get a cygwin build going, but as I'm sure
> you would expect, that will take longer.
This toolchain certainly seems to have resolved the SH3 build problems I
reported earlier. Thanks. Was adding "m3" to the list of multilibs at
config.gcc:2286 the only change required?
There is a remaining issue with linking the cxxsupp test in particular
(eg target cq7750, default template):
> sh-elf-gcc -L/var/local/build/ecos-new/install/lib -Ttarget.ld -o /var/local/build/ecos-new/install/tests/infra/current/tests/cxxsupp tests/cxxsupp.o -mb -m3 -ggdb -nostdlib -Wl,-static -Wl,--fatal-warnings
> /var/local/releng/release-3.0/targetbuild/tools/gnutools/sh-elf/bin/../lib/gcc/sh-elf/4.3.2/../../../../sh-elf/bin/ld: error: no memory region specified for loadable section `.eh_frame'
> collect2: ld returned 1 exit status
John Dallaway
next prev parent reply other threads:[~2009-01-21 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 19:48 John Dallaway
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 [this message]
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=4977B0E2.3040806@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).