From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Ray Bryant <raybry@sgi.com>,
alexn@telia.com, linux-kernel@vger.kernel.org
Subject: Re: lockmeter in 2.6.9-rc2-mm2
Date: Thu, 23 Sep 2004 21:34:32 -0700 [thread overview]
Message-ID: <20040924043432.GV9106@holomorphy.com> (raw)
In-Reply-To: <20040924042807.GU9106@holomorphy.com>
Ray Bryant <raybry@sgi.com> wrote:
>>> Does the x86_64 stuff compile now?
On Thu, Sep 23, 2004 at 09:21:06PM -0700, Andrew Morton wrote:
>> yup. I do regular x86 and x86_64 allfooconfig builds. I'd do so on
>> sparc64/ppc64/ia64 too, if they had a chance of compiling :(
On Thu, Sep 23, 2004 at 09:28:07PM -0700, William Lee Irwin III wrote:
> All it takes is grunt work to fix these; so how badly do you want them
> fixed?
FWIW, AFAICT x86-64 doesn't build with allyesconfig either. I use the
following to carry out allyesconfig compiletests.
Index: mm2-2.6.9-rc2/arch/x86_64/boot/tools/build.c
===================================================================
--- mm2-2.6.9-rc2.orig/arch/x86_64/boot/tools/build.c 2004-09-12 22:33:54.000000000 -0700
+++ mm2-2.6.9-rc2/arch/x86_64/boot/tools/build.c 2004-09-23 09:34:48.177166616 -0700
@@ -151,9 +151,6 @@
fprintf (stderr, "System is %d kB\n", sz/1024);
sys_size = (sz + 15) / 16;
/* 0x40000*16 = 4.0 MB, reasonable estimate for the current maximum */
- if (sys_size > (is_big_kernel ? 0x40000 : DEF_SYSSIZE))
- die("System is too big. Try using %smodules.",
- is_big_kernel ? "" : "bzImage or ");
while (sz > 0) {
int l, n;
next prev parent reply other threads:[~2004-09-24 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 4:17 lockmeter in 2.6.9-rc2-mm2 Ray Bryant
2004-09-24 4:20 ` William Lee Irwin III
2004-09-24 4:21 ` Andrew Morton
2004-09-24 4:28 ` William Lee Irwin III
2004-09-24 4:34 ` William Lee Irwin III [this message]
2004-09-24 4:36 ` Andrew Morton
2004-09-30 4:01 ` Ray Bryant
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=20040924043432.GV9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raybry@sgi.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