public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Building RedBoot for SH3 targets with new toolchain
Date: Wed, 21 Jan 2009 22:33:00 -0000	[thread overview]
Message-ID: <4977A2A8.1030608@eCosCentric.com> (raw)
In-Reply-To: <49779CC3.2000202@dallaway.org.uk>

John Dallaway wrote:
> Hi Jifl
> 
> Jonathan Larmour wrote:
> 
> [ snip ]
> 
>> So it's not built in an sh2 multilib. Therefore we will need to build an
>> sh3 multilib. Bummer. It needs to be added at line 2286 of config.gcc. I'm
>> rebuilding for linux now, so you can try it out when that's done and I've
>> packaged it up, but you may want to add this to any todo list you've got to
>> be sure it's tracked.
> 
> Thanks for the rapid response. At least the solution is clear. Of
> course, I will be happy to try the new tools out.
> 
> You should find some shell scripts on snitch in the base of the
> toolchains build directory hierarchy which will help with
> building/packaging sourceware toolchains. They will need minor tweaking
> for an "sh-elf only" spin.

Already seen and tweaked in fact.

>> If that build is ok, I'll have the grief of trying to
>> rebuild the cygwin version.
> 
> Similarly, there are scripts on mug for building/packaging sourceware
> toolchains in the Cygwin /gnutools directory hierarchy.

Hadn't seen those. I'll poke when it comes to that.

> I could offer to build the revised sh-elf toolchains here, but it does
> seem preferable to use the same hosts for building all the toolchains to
> ensure consistency.

You wouldn't have a good glibc version to use for backward compatibility
anyway. (Unless you go and install something old somewhere temporarily).

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.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

  reply	other threads:[~2009-01-21 22:33 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 [this message]
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=4977A2A8.1030608@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).