public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jarek Poplawski <jarkao2@o2.pl>
Subject: Re: [PATCH] Documentation/Changes -> Documentation/Requirements
Date: Fri, 30 Nov 2007 10:20:10 -0800	[thread overview]
Message-ID: <4750545A.2030605@zytor.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711301256520.7197@localhost.localdomain>

Robert P. J. Day wrote:
>> +
>> +Kernel Compilation Requirements
>> +===============================
>> +
>> +On all systems, minimal requirements (see below for additional notes):
>> +
>> +o  Gnu C                  3.2                     # gcc --version
>> +o  Gnu make               3.79.1                  # make --version
>> +o  binutils               2.12                    # ld -v
>> +o  Gnu bc                 1.06                    # bc -v
> 
> you need bc?  for what?  i just did a defconfig build for x86 with no
> need for bc.
> 

The whole motivation for this was to get a place to document that a 
previous patch uses bc.

>> +o  Perl                   5.6.0(?)                # perl -v
> 
> if you mention perl, you should also mention sed and awk, no?  and
> perhaps suggest running scripts/ver_linux.

Please submit patches.

	-hpa

  reply	other threads:[~2007-11-30 18:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  0:19 [PATCH] Avoid overflows in kernel/time.c H. Peter Anvin
2007-11-30  1:54 ` Andrew Morton
2007-11-30  3:01   ` H. Peter Anvin
2007-11-30  3:27   ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30  3:32   ` [PATCH] Documentation/Changes -> Documentation/Requirements (resend without truncated comment text) H. Peter Anvin
2007-11-30  7:16     ` Jarek Poplawski
2007-11-30 17:40       ` H. Peter Anvin
2007-11-30 17:47       ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 18:09         ` Robert P. J. Day
2007-11-30 18:20           ` H. Peter Anvin [this message]
2007-11-30  1:59 ` [PATCH] Avoid overflows in kernel/time.c Chris Snook
2007-11-30  3:04   ` H. Peter Anvin
2007-11-30  3:40     ` Arjan van de Ven
2007-11-30  3:54       ` H. Peter Anvin
2007-12-02 18:37         ` Pavel Machek
2007-12-03 14:53         ` Jan Engelhardt
2007-12-10 16:37           ` H. Peter Anvin
2007-12-01  0:33 ` Adrian Bunk
2007-12-01  4:19   ` H. Peter Anvin
2007-12-01 13:20   ` Alan Cox
2007-12-01 13:33     ` Alan Cox
2007-12-02  1:53     ` H. Peter Anvin
2007-12-07  0:22   ` Jeremy Fitzhardinge
2007-12-04 11:29 ` Andrew Morton
2007-12-10 16:46   ` H. Peter Anvin
2007-12-10 18:59   ` H. Peter Anvin
2007-12-10 22:04     ` Andrew Morton

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=4750545A.2030605@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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