From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 requires x86_64?
Date: Mon, 30 Jan 2006 19:34:21 -0800 [thread overview]
Message-ID: <29495f1d0601301934x1f4b7925w19261f457117637a@mail.gmail.com> (raw)
In-Reply-To: <43DED532.5060407@tlinx.org>
On 1/30/06, L. A. Walsh <lkml@tlinx.org> 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
You didn't say which kernel, but it looks like you didn't do a make
clean/mrproper before trying to build just an i386 kernel? Did you
build an x86_64 kernel at some point from the same tree?
I think that include/asm is pointing to asm-x86_64, which, if you
removed it, is why the compiler can't find said file.
Thanks,
Nish
next prev parent reply other threads:[~2006-01-31 3:34 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
2006-01-31 13:02 ` Steven Rostedt
2006-02-01 2:56 ` L. A. Walsh
2006-01-31 3:34 ` Nish Aravamudan [this message]
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=29495f1d0601301934x1f4b7925w19261f457117637a@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--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).