From: Chris White <webmaster@securesystem.info>
To: linux-kernel@vger.kernel.org
Subject: amd64 and 2.6.9 kernel missing asm/kgdb.h
Date: Wed, 20 Oct 2004 01:31:45 +0900 [thread overview]
Message-ID: <41754171.2030002@securesystem.info> (raw)
Greetings,
Not myself but someone else had this issue while compiling on an amd64
system.
CC arch/x86_64/ia32/ia32_signal.o
CC arch/x86_64/ia32/tls32.o
CC arch/x86_64/ia32/ia32_binfmt.o
CC arch/x86_64/ia32/fpu32.o
CC arch/x86_64/ia32/ptrace32.o
AS arch/x86_64/ia32/vsyscall-sysenter.o
SYSCALL arch/x86_64/ia32/vsyscall-sysenter.so
AS arch/x86_64/ia32/vsyscall-syscall.o
In file included from include/asm/cache.h:7,
from include/asm/segment.h:4,
from arch/x86_64/ia32/vsyscall-syscall.S:7:
include/linux/config.h:6:22: asm/kgdb.h: No such file or directory
make[1]: *** [arch/x86_64/ia32/vsyscall-syscall.o] Error 1
make: *** [arch/x86_64/ia32] Error 2
I checked the 2.6.9 tree and the file does appear to be missing. Thanks
ahead of time for any assistance in the matter. Feel free to rough me
up a bit if I'm sending out a duplicate issue, but I didn't quite see
anything of this sort while searching throught the rather lengthy 30,000
or so archived messages I have :).
Chris White
reply other threads:[~2004-10-20 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41754171.2030002@securesystem.info \
--to=webmaster@securesystem.info \
--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