All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Erik Jansson <erja9907@student.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile problem in vmalloc.h
Date: Thu, 22 Nov 2001 01:03:32 -0200	[thread overview]
Message-ID: <20011122010332.G2216@conectiva.com.br> (raw)
In-Reply-To: <3BFA9F2D.98FB7F72@student.uu.se>
In-Reply-To: <3BFA9F2D.98FB7F72@student.uu.se>

Em Tue, Nov 20, 2001 at 07:21:33PM +0100, Erik Jansson escreveu:
> Hi all!
> 
> I've looked and asked around for a while about this, but I can't seem to
> find the answer. Maybe you know what's up.
> 
> I'm compiling a driver that's not part of the kernel tree (but it's GPL
> anyway). It compiles nicely against the 2.4.8 kernel tree, but fails
> with both 2.4.10 and 2.4.14. Those are the only ones that I've tried
> though.
> 
> I'm using clean sources (nothing patched, make mrproper; make clean;
> make config; make bzImage etc).
> 
> I'm using gcc version 2.95.4 20010902 (Debian prerelease).
> 
> The error I get looks like this:
> 
> gcc -c -o ./src/proc.o ./src/proc.c -D__KERNEL__ -DMODULE -O2 -Wall
> -Wstrict-pro
> totypes -Wpointer-arith -I /usr/src/linux/include  -DCAN_DEBUG
> In file included from /usr/src/linux/include/asm/io.h:46,
>                  from src/../include/main.h:11,
>                  from ./src/proc.c:25:
> /usr/src/linux/include/linux/vmalloc.h: In function `vmalloc':
> /usr/src/linux/include/linux/vmalloc.h:35: `boot_cpu_data_Rsmp_0657d037'

Try adding this:

#include <linux/module.h>

to your driver, of course before the '#include <linux/vmalloc.h>' line 8)

- Arnaldo

      reply	other threads:[~2001-11-22  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 18:21 Compile problem in vmalloc.h Erik Jansson
2001-11-22  3:03 ` Arnaldo Carvalho de Melo [this message]

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=20011122010332.G2216@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=erja9907@student.uu.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.