Linux OpenRISC platform development
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Crosstool/kbuild-all toolchain updates
Date: Sun, 19 Feb 2017 11:49:23 -0600	[thread overview]
Message-ID: <20170219174923.GI21840@gate.crashing.org> (raw)
In-Reply-To: <20170219132637.gjv26w7w5sses2fi@wfg-t540p.sh.intel.com>

Hi!

On Sun, Feb 19, 2017 at 09:26:37PM +0800, Fengguang Wu wrote:
> An uptodate crosstool and reasonable active maintainer would be very
> welcome. I'll sure be a heavy user. In the past year when crosstool is
> not updated to gcc-6, we've resorted to using debian packages for some
> ARCHs and building our own cross compliers for the other ARCHs. The
> latter are based on Segher's buildall tools (CCed). The private builds
> may work for us in short term, however is obvious not a satisfactory
> solution.

Buildall supports GCC only, and this is not likely to change.

The primary usecase for buildall is for my own GCC testing.  All patches
are welcome, but I'm not likely to apply them if they make it harder to
use the tools for what their goal is.  I'm certainly not going to apply
patches to other trees from the scripts, etc.

Buildall itself is still maintained.  It does not get very many updates
but that is because it is close to perfect ;-)

On the other hand I'll be happy to help wherever I can.  Just Cc: me on
whatever comes up.


Segher

  parent reply	other threads:[~2017-02-19 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 22:44 [OpenRISC] Crosstool/kbuild-all toolchain updates Stafford Horne
2017-02-19  8:20 ` Stafford Horne
2017-02-19 13:26 ` Fengguang Wu
2017-02-19 15:55   ` Guenter Roeck
2017-02-19 17:49   ` Segher Boessenkool [this message]
2017-02-23 13:35     ` Stafford Horne

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=20170219174923.GI21840@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=openrisc@lists.librecores.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