public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: John Donnelly <jpd_hp_linux_scsi@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 2.6-test4: mpspec.h:6:25: mach_mpspec.h: Missing file
Date: Fri, 5 Sep 2003 15:02:08 +0100	[thread overview]
Message-ID: <20030905140208.GI18654@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030904221927.22799.qmail@web20703.mail.yahoo.com>

On Thu, Sep 04, 2003 at 03:19:27PM -0700, John Donnelly wrote:
> 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 the  gcc command line, sample
> and the fatal error that mach_mpspec.h can't be found.

I think you'd be much better off integrating your code into the tree as
a drivers/scsi/ subdirectory; see how little Makefile code has to be
written for (eg) sym53c8xx_2/

> 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 ?

There are many bits of the 2.6 build system that work differently from 2.4,
see below..

> In file included from /work/src/linux-2.6.0-test4/include/asm/smp.h:18,
>                  from /work/src/linux-2.6.0-test4/include/linux/smp.h:17,
>                  from /work/src/linux-2.6.0-test4/include/linux/topology.h:33,
>                  from /work/src/linux-2.6.0-test4/include/linux/mmzone.h:294,
>                  from /work/src/linux-2.6.0-test4/include/linux/gfp.h:4,
>                  from /work/src/linux-2.6.0-test4/include/linux/slab.h:15,
>                  from test.c:8:
> /work/src/linux-2.6.0-test4/include/asm/mpspec.h:6:25: mach_mpspec.h: No such file or directory
> /work/src/linux-2.6.0-test4/include/asm/mpspec.h:8: `MAX_MP_BUSSES' undeclared here (not in a function)
> 
>  gcc -g -D__KERNEL__ -DMODULE -I/work/src/linux-2.6.0-test4/include \
> 	-I/work/src/linux-2.6.0-test4/drivers/scsi -c test.c

Here's the command line for a normal file (as compiled on my laptop,
your tree will no doubt use subtly diffeent options.  Use `make V=1'
to see the verbose output from make)

  gcc -Wp,-MD,mm/.fadvise.o.d -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -Iinclude/asm-i386/mach-default -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc -iwithprefix include    -DKBUILD_BASENAME=fadvise -DKBUILD_MODNAME=fadvise -c -o mm/fadvise.o mm/fadvise.c

For building outside the tree, I guess you wouldn't need some of it, but
I think your problem is caused by missing -Iinclude/asm-i386/mach-default

But build inside the tree.  You're going to want to do that eventually
anyway and it saves you from this problem and several like it.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-09-05 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030902231812.03fae13f.akpm@osdl.org>
2003-09-03 17:02 ` 2.6.0-test4-mm5: SCSI imm driver doesn't compile Adrian Bunk
2003-09-04 13:30   ` Arnaldo Carvalho de Melo
2003-09-04 13:52     ` Jan-Benedict Glaw
2003-09-04 14:30       ` Christoph Hellwig
2003-09-04 14:54         ` Jan-Benedict Glaw
2003-09-04 17:50     ` [new patch] " Adrian Bunk
2003-09-04 22:19   ` 2.6-test4: mpspec.h:6:25: mach_mpspec.h: Missing file John Donnelly
2003-09-05 14:02     ` Matthew Wilcox [this message]
2003-09-05 17:12       ` 2.6-test4: " jd

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=20030905140208.GI18654@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=jpd_hp_linux_scsi@yahoo.com \
    --cc=linux-scsi@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