From: John Spencer <maillist-linux@barfooze.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Rob Landley <rob@landley.net>
Subject: Re: [PATCH 0/3] build linux-next without perl
Date: Wed, 27 Feb 2013 20:50:55 +0100 [thread overview]
Message-ID: <512E639F.4010904@barfooze.de> (raw)
In-Reply-To: <20130227185328.GA27243@merkur.ravnborg.org>
On 02/27/2013 07:53 PM, Sam Ravnborg wrote:
> On Wed, Feb 27, 2013 at 05:55:31PM +0100, John Spencer wrote:
>> Rob Landley wrote:
>>> Before 2.6.25 building Linux never required perl. This patch series
>> removes
>>> the requirement from basic kernel builds (tested on i686, x86_64, arm,
>>>
>> mips,
>>> powerpc, sparc, sh4, and m68k). Now updated to 3.8-rc1.
>>
>> using this patch series since 2.6.32 in sabotage linux, it is highly
>> useful and it's about time to get it merged.
>> tested against linux 3.8, works perfectly.
>
> Why do you apply this patch serie to sabotage linux?
>
> Sam
>
it allows me to build the kernel as soon as the minimal base system is
bootstrapped. building perl takes about as long as the whole base system
(busybox,gcc,binutils,make) together, so having that dependency removed
is a huge relief.
btw, bootstrap-linux [1] uses this patch series as well.
[1] https://github.com/pikhq/bootstrap-linux
next prev parent reply other threads:[~2013-02-27 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:55 [PATCH 0/3] build linux-next without perl John Spencer
2013-02-27 18:53 ` Sam Ravnborg
2013-02-27 19:50 ` John Spencer [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 5:57 Rob Landley
2013-02-27 21:51 ` Andrew Morton
2013-02-28 4:01 ` Rob Landley
2013-02-28 4:48 ` Rob Landley
2013-02-28 6:47 ` Geert Uytterhoeven
2013-02-28 8:44 ` Michal Marek
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=512E639F.4010904@barfooze.de \
--to=maillist-linux@barfooze.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=sam@ravnborg.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