From: Gerrit Huizenga <gerrit@sequent.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Problem while compiling a module
Date: Wed, 12 Jul 2000 17:43:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205198@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205196@msgid-missing>
I had a similar problem simply compiling the kernel from the latest
redhat distro for ia64. The problem was a couple of missing underscores
in include/linux/version.h on _module_up -> __module_up and _module_smp ->
__module_smp.
My "revised" version is as follows (sorry, I toasted the orig or I'd
send diffs, although they'd probably be larger. ;-):
#include <linux/rhconfig.h>
#if defined(__module_up)
#define UTS_RELEASE "2.4.0-0.8"
#endif
#if defined(__module_smp)
#define UTS_RELEASE "2.4.0-0.8smp"
#endif
#define LINUX_VERSION_CODE 132096
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
gerrit
> Hi,
>
> I'm trying to make a device driver on an Itanium, and while including
> <linux/module.h>, with the -DMODULE flag, I get the following problem:
>
> /usr/include/linux/module.h:223: parse error before `UTS_RELEASE'
>
> The line itself is:
>
> static const char __module_kernel_version[]
> __attribute__((section(".modinfo"))) =
> "kernel_version=" UTS_RELEASE;
>
> Has anybody got a hint to solve this problem? (removing the line is a bad
> idea as I'm using UTS_RELEASE...)
>
>
> Geraud
>
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
prev parent reply other threads:[~2000-07-12 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 11:20 [Linux-ia64] Problem while compiling a module G\351raud Krawezik
2000-07-12 14:08 ` Jes Sorensen
2000-07-12 17:43 ` Gerrit Huizenga [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=marc-linux-ia64-105590678205198@msgid-missing \
--to=gerrit@sequent.com \
--cc=linux-ia64@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