From: Peter Hurley <peter@hurleysoftware.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 09:02:34 -0400 [thread overview]
Message-ID: <53C131EA.2020502@hurleysoftware.com> (raw)
In-Reply-To: <20140712112012.69befaf0@canb.auug.org.au>
On 07/11/2014 09:20 PM, Stephen Rothwell wrote:
> 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 ...
Hi Stephen,
Thanks for the link. I had found Shuah Khan's slideshow pdf on cross-compiler
packages earlier and so have already started down that path.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-07-12 13:02 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
2014-07-12 13:02 ` Peter Hurley [this message]
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=53C131EA.2020502@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).