From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i386 requires x86_64?
Date: Mon, 30 Jan 2006 19:31:29 -0800 [thread overview]
Message-ID: <20060130193129.19f04e6f.rdunlap@xenotime.net> (raw)
In-Reply-To: <43DED532.5060407@tlinx.org>
On Mon, 30 Jan 2006 19:10:42 -0800 L. A. Walsh wrote:
> Generating a new kernel and wanted to delete the unrelated architectures.
>
> Is the i386 supposed to depend on the the x86_64 architecture?
>
> In file included from arch/i386/kernel/acpi/earlyquirk.c:8:
> include/asm/pci-direct.h:1:35: asm-x86_64/pci-direct.h: No such file or
> directory
> arch/i386/kernel/acpi/earlyquirk.c: In function `check_acpi_pci':
> arch/i386/kernel/acpi/earlyquirk.c:34: warning: implicit declaration of
> function `read_pci_config'
> make[2]: *** [arch/i386/kernel/acpi/earlyquirk.o] Error 1
> make[1]: *** [arch/i386/kernel/acpi] Error 2
> make: *** [arch/i386/kernel] Error 2
> make: *** Waiting for unfinished jobs....
>
> I'm generating for a pentium-3 based computer. Should that
> include x86_64 bits?
Yes, there are bits in i386 that use x86_64 and there are
bits in x86_64 that use i386 code, so that the source code
won't have to be duplicated.
---
~Randy
next prev parent reply other threads:[~2006-01-31 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 3:10 i386 requires x86_64? L. A. Walsh
2006-01-31 3:31 ` Randy.Dunlap [this message]
2006-01-31 13:02 ` Steven Rostedt
2006-02-01 2:56 ` L. A. Walsh
2006-01-31 3:34 ` Nish Aravamudan
2006-01-31 8:54 ` Jesper Juhl
2006-01-31 13:17 ` Steven Rostedt
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=20060130193129.19f04e6f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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).