All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	Dave Jones <davej@redhat.com>, David Howells <dhowell@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Josh Boyer <jwboyer@redhat.com>, Michal Marek <mmarek@suse.cz>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Sam Ravnborg <sam@ravnborg.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vince Weaver <vincent.weaver@maine.edu>,
	x86@kernel.org, Zheng Yan <zheng.z.yan@intel.com>
Subject: Re: [PATCH 0/3] build linux-next without perl
Date: Wed, 27 Feb 2013 22:48:47 -0600	[thread overview]
Message-ID: <1362026927.15531.2@driftwood> (raw)
In-Reply-To: <20130227135155.c04453db.akpm@linux-foundation.org> (from akpm@linux-foundation.org on Wed Feb 27 15:51:55 2013)

On 02/27/2013 03:51:55 PM, Andrew Morton wrote:
> On Tue, 26 Feb 2013 21:57:52 -0800 (PST)
> Rob Landley <rob@landley.net> 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.
> >
> > Note, this removes perl from the _build_ environment, not from the  
> _development_
> > environment. This is approximately the same logic behind "make  
> menuconfig"
> > requiring curses but "make oldconfig" not requiring curses.  
> Including
> > zconf.lex.c_shipped in kconfig and then requiring perl makes no  
> sense.
> >
> > ...
> >
> > Mostly people just copy the patches into their local projects (ala
> > https://github.com/rofl0r/sabotage/tree/master/KEEP ) but I'm  
> reposting
> > them to linux-kernel after Gentoo considered using these patches,  
> but didn't
> > because they weren't upstream:
> >   https://bugs.gentoo.org/show_bug.cgi?id=421483
> 
> Sitting here scratching head wondering why you-need-perl is a problem
> for anyone.
> 
> That gentoo bug report provides some explanation: "perl was removed
> from @system".  But I expect other people have different reasons.
> 
> IOW, please better describe the motivation for this patchset.

P.S. A much shorter reply than mine, from David Anders:

https://plus.google.com/101339419642360856354/posts/AyRnz2REq8C

Rob

  parent reply	other threads:[~2013-02-28  4:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  5:57 [PATCH 0/3] build linux-next without perl Rob Landley
2013-02-27  5:57 ` [PATCH 1/3] convert mkcapflags.pl to mkcapflags.sh Rob Landley
2013-02-27  5:58 ` [PATCH 2/3] convert timeconst.pl to mktimeconst.c Rob Landley
2013-02-27  5:58 ` [PATCH 3/3] convert headers_install.pl to headers_install.sh Rob Landley
2013-02-28  8:19   ` Michal Marek
2013-03-01  5:07     ` Rob Landley
2013-04-09 10:52     ` Michal Marek
2013-04-11 16:25       ` Rob Landley
2013-04-11 19:20         ` Michal Marek
2013-02-27 21:51 ` [PATCH 0/3] build linux-next without perl Andrew Morton
2013-02-28  4:01   ` Rob Landley
2013-02-28  4:48   ` Rob Landley [this message]
2013-02-28  6:47   ` Geert Uytterhoeven
2013-02-28  8:44   ` Michal Marek
  -- strict thread matches above, loose matches on Subject: below --
2013-02-27 16:55 John Spencer
2013-02-27 18:53 ` Sam Ravnborg
2013-02-27 19:50   ` John Spencer

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=1362026927.15531.2@driftwood \
    --to=rob@landley.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davej@redhat.com \
    --cc=dhowell@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@suse.de \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jwboyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmarek@suse.cz \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.weaver@maine.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=x86@kernel.org \
    --cc=zheng.z.yan@intel.com \
    /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.