From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Peter Hurley <peter@hurleysoftware•com>
Cc: Greg KH <greg@kroah•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the tty.current tree
Date: Sat, 12 Jul 2014 11:20:12 +1000 [thread overview]
Message-ID: <20140712112012.69befaf0@canb.auug.org.au> (raw)
In-Reply-To: <53BFFD90.5010405@hurleysoftware.com>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi Peter,
On Fri, 11 Jul 2014 11:06:56 -0400 Peter Hurley <peter@hurleysoftware•com> wrote:
>
> Sorry about that. I don't have a full cross-compiler setup for
> build testing. Looks like that's something I'm going to have to add.
see https://www.kernel.org/pub/tools/crosstool/
These are only good for building the kernel (no libc).
You don't necessarily need to build the whole kernel but often just
building the particular drivers is enough. Especially if they are
directly modified ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-12 1:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 1:21 linux-next: build failure after merge of the tty.current tree Stephen Rothwell
2014-07-11 2:36 ` [PATCH] serial: imx: Fix build breakage Peter Hurley
2014-07-12 0:42 ` Greg Kroah-Hartman
2014-07-12 2:00 ` Randy Dunlap
2014-07-12 2:09 ` Stephen Rothwell
2014-07-12 2:16 ` Greg Kroah-Hartman
2014-07-12 2:39 ` Randy Dunlap
2014-07-12 13:11 ` Peter Hurley
2014-07-11 15:06 ` linux-next: build failure after merge of the tty.current tree Peter Hurley
2014-07-12 1:20 ` Stephen Rothwell [this message]
2014-07-12 13:02 ` Peter Hurley
2014-07-15 17:49 ` Peter Hurley
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 20:58 Stephen Rothwell
2023-01-19 21:49 ` Marek Vasut
2023-01-21 7:30 ` Greg KH
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=20140712112012.69befaf0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=peter@hurleysoftware$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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