From: Christoph Pleger <Christoph.Pleger@uni-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 10 GB in Opteron machine
Date: Fri, 22 Jul 2005 13:37:46 +0200 [thread overview]
Message-ID: <20050722133746.67e5f5d3.Christoph.Pleger@uni-dortmund.de> (raw)
In-Reply-To: <20050722103955.GI30510@unthought.net>
Hello,
On Fri, 22 Jul 2005 12:39:55 +0200
Jakob Oestergaard <jakob@unthought.net> wrote:
> > 1. Is it possible to compile a 64-bit kernel on a 32-bit machine (or
> > at least on a 64-bit machine with 32-bit software) and if yes, how
> > can I do that?
>
> Yes. On Debian Sarge, I have a few wrapper scripts to accomplish it -
> all attached to this mail - just untar them in /usr/local/bin on a
> standard x86 32-bit Sarge distro. Use 'kmake' instead of 'make' when
> you are working with your kernel source (eg. 'kmake menuconfig',
> 'kmake all')
>
> Sarge comes with all the necessary toolchain support to build a 64-bit
> kernel.
>
> It should be equally possible on most other distros of course, I just
> haven't felt the urge to go waste my time with them :)
I am also using Debian sarge. I extracted the tarfile to /usr/local/bin
end executed "kmake menuconfig". Everything seemed fine so far. But a
few seconds after starting the compilation (kmake bzImage) I got this
error message:
In file included from <snip>
...
<snip>
include/asm/mpspec.h:6:25: mach_mpspec.h: No such file or directory
Hm. I understand why that file cannot be found: It only exists in the
asm-i386 directory. But why does the compilation process look for a file
that belongs to i386, but not to x86_64?
Christoph
next prev parent reply other threads:[~2005-07-22 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 8:55 Christoph Pleger
2005-07-22 9:05 ` Jeff Garzik
2005-07-22 9:31 ` Christoph Pleger
2005-07-22 10:17 ` Bernd Petrovitsch
2005-07-22 10:17 ` Bernd Petrovitsch
2005-07-22 10:39 ` Jakob Oestergaard
2005-07-22 11:37 ` Christoph Pleger [this message]
2005-07-22 13:55 ` Jakob Oestergaard
2005-07-25 10:41 ` Christoph Pleger
2005-07-22 12:57 ` Stephen Frost
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=20050722133746.67e5f5d3.Christoph.Pleger@uni-dortmund.de \
--to=christoph.pleger@uni-dortmund.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
all inboxes | Powered by JetHome®