From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
Chris Snook <csnook@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Avoid overflows in kernel/time.c
Date: Mon, 10 Dec 2007 08:37:24 -0800 [thread overview]
Message-ID: <475D6B44.8050707@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711302017100.18767@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Nov 29 2007 19:54, H. Peter Anvin wrote:
>> Arjan van de Ven wrote:
>>>> Anyway, I don't think compiling bc is hard on anything which has a C
>>>> compiler.
>>> alternative is to just also ship the precomputed values ;-)
>>>
>> Oh, come on... it's not like bc is some obscure thing. It's a POSIX utility.
>
> People try building linux on not-so-posix systems these days...
>
Are you talking about Cygwin (which has bc prepackaged)? Even if not, I
would be *extremely* surprised to find something that can build the
Linux kernel which can't build GNU bc out of the box.
In fact, I would be rather surprised to find that the Linux kernel
builds on anything which doesn't come prepackaged with bc.
-hpa
next prev parent reply other threads:[~2007-12-10 16:42 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
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 [this message]
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=475D6B44.8050707@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=csnook@redhat.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).