All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Hershberger <joe.hershberger@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] tools: get-toolchais: a tool to get cross-tools for all architectures
Date: Tue, 19 May 2015 10:28:13 -0500	[thread overview]
Message-ID: <CANr=Z=bfKkLYK+qynRPfnYE3YKhqr+2=jO3h5p5UpZNFbX384w@mail.gmail.com> (raw)
In-Reply-To: <1431687670-23515-1-git-send-email-yamada.masahiro@socionext.com>

On Fri, May 15, 2015 at 6:01 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> When we send patches, we are supposed to test them by build utilities
> such as MAKEALL, buildman.  When we want to test global changes, the
> first hurdle is, I think, to collect toolchains for all the architectures.
>
> We have some documents about build utilities, but I have not seen any
> official information about how to get the suitable cross-tools.
> Of course, it is possible to build them from sources, but it is not
> necessarily feasible.
>
> Fortunately, the kernel.org site provides us pre-built toolchains, but
> some architectures are missing.  Also, some boards fail to build with
> the kernel.org tools.  We sometimes see, "where can I get the compiler
> for this architecture?" things on the ML.  We should be able to prepare
> cross-compilers more easily.
>
> It is true that buildman provides --fetch-arch option for downloading
> kernel.org toolchains, but it does not have access to others.  And what
> we really want to know is most likely how to get compilers for such minor
> architectures as kernel.org does not provide.
>
> This tool intends to be more generic design without hard-coding such
> kernel.org things.
>
> To achieve that, this tool consists of two files:
> Python script (this file) and the database file containing URLs of tarballs.
>
> We just need to update the latter when new version compilers are released
> (or better compilers are found.)  The file is in the form of RFC 822 for
> easier editing.
>
> The script only uses Python libraries, not relies on external programs
> although it displays wget-like log when downloading tarballs.  :-)
>
> This is RFC because I am thinking it can be more brushed up.
> If the basis idea is OK, I will improve code, add more comments.
>
> Note this script is written in Python 3 and only works on Python 3.3
> or later.  I do not think it is too much limitation, but some popular
> distributions under support might include older version.  For example,
> looks like Ubuntu 12.04 LTS is shipped with Python 3.2.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---

Also, in case you didn't notice, you have a typo in the subject of the
patch. "toolchais".

-Joe

      parent reply	other threads:[~2015-05-19 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 11:01 [U-Boot] [RFC PATCH] tools: get-toolchais: a tool to get cross-tools for all architectures Masahiro Yamada
2015-05-15 19:52 ` Joe Hershberger
2015-05-16  4:58   ` Masahiro Yamada
2015-05-17 17:50     ` Simon Glass
2015-05-19  5:04       ` Masahiro Yamada
2015-05-19 17:16         ` Simon Glass
2015-05-19 18:13           ` Joe Hershberger
2015-05-19 18:17             ` Simon Glass
2015-05-20  4:50               ` Masahiro Yamada
2015-05-19 15:28 ` Joe Hershberger [this message]

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='CANr=Z=bfKkLYK+qynRPfnYE3YKhqr+2=jO3h5p5UpZNFbX384w@mail.gmail.com' \
    --to=joe.hershberger@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.