From: Jason Cooper <jason@lakedaemon.net>
To: Olof Johansson <olof@lixom.net>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference
Date: Sun, 24 Aug 2014 15:16:18 -0400 [thread overview]
Message-ID: <20140824191618.GB12769@titan.lakedaemon.net> (raw)
In-Reply-To: <20140824191415.GA12769@titan.lakedaemon.net>
On Sun, Aug 24, 2014 at 03:14:15PM -0400, Jason Cooper wrote:
> On Sun, Aug 24, 2014 at 11:47:47AM -0700, Olof Johansson wrote:
> ...
> > I have traditionally been using Segher's buildall
> > (http://git.infradead.org/users/segher/buildall.git) to build and
> > populate toolchains locally, and that will no longer be enough. Unless
> > someone convinces Segher to improve his scripts, of course. :)
>
> fwiw, I've been using Mike Frysinger's crossdev utility on gentoo for
> many years. While it's tied closely to portage (can't live without it),
> it has the advantage of automatic toolchain updates during regular
> system updates.
I should also mention that I've reliably used it for years to make
minimalist rootfs's, either initrds, or rootfs's on flash. Which is why
I thought it was relevant to the conversation.
> Currently, I have the following on my build system:
>
> aarch64-unknown-linux-gnu-
>
> arm-none-linux-gnueabi-
> arm-none-linux-uclibceabi-
>
> powerpc-none-linux-gnueabi-
>
> mips-none-linux-gnueabi-
> mips-pc-linux-gnu-
>
> s390-none-linux-gnueabi-
>
> i586-pc-linux-gnu-
> x86_64-pc-linux-gnu-
>
> Admittedly, I use the arm- one the most.
>
> A while ago I looked at adding crossdev to gentoo-prefix (install gentoo
> inside another OS, like OS X, or debian) which would then make the
> utility much more useful. But I never found the time to make it a
> reality. :(
thx,
Jason.
prev parent reply other threads:[~2014-08-24 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` Grant Likely
2014-08-22 17:59 ` Shuah Khan
2014-08-22 18:08 ` Amit Kucheria
2014-08-28 21:54 ` Shuah Khan
2014-08-23 13:35 ` Bird, Tim
2014-08-23 21:12 ` Grant Likely
2014-08-30 1:09 ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30 2:55 ` Shuah Khan
2014-08-30 5:15 ` Konstantin Ryabitsev
2014-08-23 8:12 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12 ` Grant Likely
2014-08-24 18:14 ` Guenter Roeck
2014-08-25 9:23 ` Grant Likely
2014-08-25 10:43 ` Guenter Roeck
2014-08-24 18:15 ` Geert Uytterhoeven
2014-08-24 18:37 ` Guenter Roeck
2014-08-24 18:47 ` Olof Johansson
2014-08-24 19:14 ` Jason Cooper
2014-08-24 19:16 ` Jason Cooper [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=20140824191618.GB12769@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lixom.net \
--cc=segher@kernel.crashing.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