mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: dead_email@nospam-mail.org
Cc: jpd_hp_linux_kernel@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6-test4: mpspec.h:6:25: mach_mpspec.h: Missing file
Date: Fri, 5 Sep 2003 10:28:40 -0700	[thread overview]
Message-ID: <20030905102840.59116fc5.rddunlap@osdl.org> (raw)
In-Reply-To: <20030904220233.79882.qmail@web60108.mail.yahoo.com>

On Thu, 4 Sep 2003 15:02:33 -0700 (PDT) j d <jpd_hp_linux_kernel@yahoo.com> wrote:

| Hi. 
| I'm trying to build a (add-on) module 
| on a machine booted from a 2.6-test4 kernel,
| And keep running into this error. I've 
| included a sample program , and gcc command
| line.
| 
| I built the kernel:
| 
| make defconfig; 
| 
| It is a 2W SMP (Compaq ML850)
| couple minor modes like enet & SCSI device
| make
| My general question is, should I include the 
| 
| -I/work/src/<build>/include/asm-i386/mach-generic/mach_mpspec.h
| 
| in my gcc command line or is my build area incorrect
| is
| some way that the correct mpspec.h file can't be found

See linux/Documentation/modules.txt and Documentation/kbuild/makefiles.txt
for how to do this properly.  Basically put your source and Makefile
in a subdir, then use this command and it builds without that error.
(Your source had a few other warnings, but it does build this way.)

Here's the Makefile that I used, with usage info in it:

# makefile for addonmodule
# Randy Dunlap, 2003-02-21
# usage:
# cd /path/to/kernel/source && make SUBDIRS=/path/to/source/addonmodule/ modules

obj-m := addonmodule.o



--
~Randy

  reply	other threads:[~2003-09-05 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 22:02 j d
2003-09-05 17:28 ` Randy.Dunlap [this message]
2003-09-05 14:38 j d

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=20030905102840.59116fc5.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=dead_email@nospam-mail.org \
    --cc=jpd_hp_linux_kernel@yahoo.com \
    --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®