mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: fengguang.wu@intel.com
Cc: Openrisc <openrisc@lists.librecores.org>,
	linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Crosstool/kbuild-all toolchain updates
Date: Wed, 1 Feb 2017 07:44:38 +0900	[thread overview]
Message-ID: <20170131224438.GD21641@lianli.shorne-pla.net> (raw)

Hi Fengguang/All,

I am working as the OpenRISC linux kernel maintainer.  Currently in
linux-next our patches are causing kbuild test robot to fail.

This is because the patches are taking advantage of 2 'new' (2 year old)
instrucions (l.swa/l.lwa) and the build robots, as far as I can tell,
use the 'make.cross' [0] build script from lkp-tests.git.  These point
to the crosstools [1] toolchains maintained by Tony.

I sent a mail to Tony who maintains the crosstools but I didn't get a
reply and it seems he is not longer working on them [1].

I think our options are:

  1. Update 'make.cross' to point somewhere else for openrisc
  2. Update and maintain crosstools

For 1. its trvial but, maybe not the best solution.

For 2. I created new crosstool builds for openrisc [3]. The way the
crosstools are maintained is via a patches.tar file and it seem a custom
buildall script.  I dont see the source for that custom script anywhere.

I am thinking I could help to update and 'opensource' the crosstool
build scripts to make it easier for everyone to update toolchains by
sending patches.

But, I would need access to crosstool on kernel.org and an OK from
everyone.

Any opinions? Questions?

-Stafford

[0] https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/sbin/make.cross
[1] https://www.kernel.org/pub/tools/crosstool/
[2] https://marc.info/?l=linux-kernel&m=146406282809809&w=1
[3] http://shorne.noip.me/crosstool/files/

             reply	other threads:[~2017-01-31 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 22:44 Stafford Horne [this message]
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
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=20170131224438.GD21641@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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

all inboxes | Powered by JetHome®