From: Tony Breeds <tony@bakeyournoodle.com>
To: Jon Masters <jcm@jonmasters.org>, Chris Smart <chris@distroguy.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: crosstool builds - https://www.kernel.org/pub/tools/crosstool/
Date: Tue, 24 May 2016 14:06:41 +1000 [thread overview]
Message-ID: <20160524040641.GD86118@thor.bakeyournoodle.com> (raw)
In-Reply-To: <6d09a289-c2da-8071-aff3-5d895692dcb6@jonmasters.org>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Thu, May 19, 2016 at 11:48:39PM -0400, Jon Masters wrote:
> Hi Tony,
>
> I'm wondering whether you know of anyone who has picked up where you
> left off, building cross toolchains for various and sundry alternative
> architectures? I wanted to download an IA64 compiler recently (really)
> and noticed that the most recent builds were against GCC 4.6.3.
Chris (on CC) is a co-worker (ish, it's complicated) that I've been nagging to
take over where I left off.
I'm sure there is a process for getting Chris access to the korg infrastructure
but in the mean time I'm *sure* he can fond somewhere to build them.
All my patches and scripts are public so go nuts :)
> Thanks in advance, and for making these before!
No problem it was fun, but (as happens in our community) I've changed focus and
can't make the time for them.
Yours Tony.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-24 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 3:48 crosstool builds - https://www.kernel.org/pub/tools/crosstool/ Jon Masters
2016-05-24 4:06 ` Tony Breeds [this message]
2016-05-24 4:41 ` Peter Hurley
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=20160524040641.GD86118@thor.bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=chris@distroguy.com \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
/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