From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org, Konrad Eisele <eiselekd@web.de>
Subject: Re: Perl in the toolchain
Date: Fri, 31 Jan 2003 21:41:32 +0100 [thread overview]
Message-ID: <20030131204132.GA1226@mars.ravnborg.org> (raw)
In-Reply-To: <20030131194837.GC8298@gtf.org>
On Fri, Jan 31, 2003 at 02:48:37PM -0500, Jeff Garzik wrote:
> On Fri, Jan 31, 2003 at 01:41:26PM -0600, Kai Germaschewski wrote:
> > Generally, we've been trying to not make perl a prequisite for the kernel
> > build, and I'd like to keep it that way. Except for some arch specific
>
> That's pretty much out the window when klibc gets merged, so perl will
> indeed be a build requirement for all platforms...
None of the perl scripts looks complicated.
Obivious question is if the same functionality could be achived by a simple
c program.
In the tool chain we use small C utilities in favour of for example
perl scripts in several places.
I would like to see perl kept out of the short-list of required programs
for the main stream kernels.
If the prize to do this is to write one or two small c tools to klibc
then I'm willing to pay that.
Sam
next prev parent reply other threads:[~2003-01-31 20:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 18:39 Perl in the toolchain Pete Zaitcev
2003-01-31 19:41 ` Kai Germaschewski
2003-01-31 19:48 ` Jeff Garzik
2003-01-31 19:55 ` Mr. James W. Laferriere
2003-01-31 20:41 ` Sam Ravnborg [this message]
2003-01-31 22:50 ` Ben Greear
2003-01-31 21:38 ` J.A. Magallon
2003-01-31 22:22 ` Sam Ravnborg
2003-01-31 23:23 ` Jeff Garzik
2003-02-01 0:29 ` H. Peter Anvin
2003-02-01 12:12 ` Sam Ravnborg
2003-01-31 23:40 ` J.A. Magallon
[not found] ` <mailman.1044055681.1939.linux-kernel2news@redhat.com>
2003-02-01 1:06 ` Pete Zaitcev
2003-02-01 6:02 ` Ryan Anderson
2003-01-31 22:51 ` Roman Zippel
2003-01-31 23:27 ` Jeff Garzik
2003-01-31 23:40 ` J.A. Magallon
2003-01-31 23:40 ` Jeff Garzik
2003-02-01 0:01 ` Roman Zippel
2003-02-01 0:05 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 20:13 Ed Vance
2003-02-01 3:28 ` Scott Robert Ladd
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=20030131204132.GA1226@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=eiselekd@web.de \
--cc=jgarzik@pobox.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox