From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Linux Mailing Lists <linux@aiind.upv.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem compiling 2.4.28 [dn_neigh.c]
Date: Tue, 23 Nov 2004 05:27:16 -0200 [thread overview]
Message-ID: <20041123072716.GC2712@logos.cnet> (raw)
In-Reply-To: <Pine.LNX.4.58.0411201948310.18643@andercheran.aiind.upv.es>
On Sat, Nov 20, 2004 at 08:16:17PM +0100, Linux Mailing Lists wrote:
>
> Hello,
>
> While compiling the lastest 2.4 kernel I stumbled on this error:
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.28/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
> -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -nostdinc
> -iwithprefix include -DKBUILD_BASENAME=dn_dev -c -o dn_dev.o dn_dev.c
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.28/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
> -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -nostdinc
> -iwithprefix include -DKBUILD_BASENAME=dn_neigh -c -o dn_neigh.o
> dn_neigh.c
> dn_neigh.c:584: `THIS_MODULE' undeclared here (not in a function)
> dn_neigh.c:584: initializer element is not constant
> dn_neigh.c:584: (near initialization for `dn_neigh_seq_fops.owner')
> make[2]: *** [dn_neigh.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.28/net/decnet'
> make[1]: *** [_modsubdir_decnet] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.28/net'
> make: *** [_mod_net] Error 2
>
> I followed the same steps as always to do the compilation:
>
> - I copied linux-2.4.27/.config to linux-2.4.28/.config
> - I made an "make oldconfig" in the 2.4.28 directory
> - Then I tried to compile the kernel and the modules, as usual, with "make
> dep; make clean; make bzImage; make modules"
>
> I Googled the archives of the list to see if someone had reported this
> error, but I didn't seem to find anything about it. I found a patch for a
> similar error (from quite a while ago) and tried it, and the compilation
> went fine.
>
> The patch is very simple, I just added the line:
>
> #include <linux/module.h>
Yep.
>
> To dn_neigh.c and ¡voilá! the compilation went without a single warning at
> that point.
>
> I got this error in three different Linux machines.
Fixed in 2.4 BK tree.
prev parent reply other threads:[~2004-11-23 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 19:16 Problem compiling 2.4.28 [dn_neigh.c] Linux Mailing Lists
2004-11-23 7:27 ` Marcelo Tosatti [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=20041123072716.GC2712@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@aiind.upv.es \
/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.