mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, hpa@zytor.com
Subject: No, you do NOT already need perl to build the kernel!
Date: Wed, 13 Feb 2008 12:15:22 -0600	[thread overview]
Message-ID: <200802131215.23297.rob@landley.net> (raw)

Please revert commit bdc807871d58285737d50dc6163d0feb72cb0dc2 because it's 
based on a false assumption:

>     At Ralf Baechle's suggestion, this version uses a Perl script to
> compute the necessary constants.  We already have dependencies on Perl for
> kernel compiles.

You do NOT need perl to build the kernel.  Perl is used in various debugging 
tools for stack checking and stuff (just like python is used in 
bloat-o-meter).  But perl is NOT required to compile the kernel, and never 
has been.  Not on x86, x86-64, arm, mips, powerpc, super hitachi, or sparc.  
(Haven't personally tested the others recently.)

I submitted a patch to _remove_ a perl dependency from the User Mode Linux 
build back in 2005.  (During the bitkeeper days, although git 
b05d85a87d9711f5f5f2eb05c79038d5d5ff1f44 updated said patch to work with 
older versions of sed).

Please don't reintroduce this.  I can recompile a system from source code 
under itself with only seven packages (linux, uClibc, busybox, gcc, binutils, 
make, bash), meaning that's the minimal environment I have to bootstrap on a 
new hardware platform in order to be able to compile my way up to a full 
distro in a self-hosting manner.  Adding perl to that would _double_ the 
complexity.  (Getting perl to cross compile requires involves medieval 
torture implements and several lewd acts with a chicken, and that's just for 
microperl...)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

                 reply	other threads:[~2008-02-13 18:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200802131215.23297.rob@landley.net \
    --to=rob@landley.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®