From: Florian Schmidt <mista.tapas@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: getting FUSD compiled with current kernels
Date: Sat, 29 Sep 2007 18:37:51 +0200 [thread overview]
Message-ID: <200709291837.51976.mista.tapas@gmx.net> (raw)
In-Reply-To: <200709291835.15489.mista.tapas@gmx.net>
On Saturday 29 September 2007, Florian Schmidt wrote:
> On Saturday 29 September 2007, Florian Schmidt wrote:
> > Hi,
> >
> > I'm trying to build FUSD [1] against current kernels [2.6.22]. I get
> > errors [2]:
>
> Oh i forgot to show the code snippets in question. I put them to the
Oh and i also forget to mention that i get the same errors when using:
KDIR=/usr/src/linux-source-2.6.22/ make
[Where the ubuntu kernel package put the source. I configured it with the
default ubuntu .config and make oldconfig]. I get one more message though:
~/source/build_stuff/fusd/kfusd$ KDIR=/usr/src/linux-source-2.6.22/ make
make -C /usr/src/linux-source-2.6.22/
SUBDIRS=/home/tapas/source/build_stuff/fusd/kfusd
EXTRA_CFLAGS=-I/home/tapas/source/build_stuff/fusd/kfusd/../include modules
make[1]: Entering directory `/usr/src/linux-source-2.6.22'
WARNING: Symbol version dump /usr/src/linux-source-2.6.22/Module.symvers
is missing; modules will have no dependencies and modversions.
CC [M] /home/tapas/source/build_stuff/fusd/kfusd/kfusd.o
/home/tapas/source/build_stuff/fusd/kfusd/kfusd.c: In function ‘to_kobj’:
/home/tapas/source/build_stuff/fusd/kfusd/kfusd.c:135: error: dereferencing
pointer to incomplete type
[...]
Regards,
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
next prev parent reply other threads:[~2007-09-29 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 16:23 Florian Schmidt
2007-09-29 16:35 ` Florian Schmidt
2007-09-29 16:37 ` Florian Schmidt [this message]
2007-09-29 17:16 ` Sam Ravnborg
2007-09-30 1:26 ` Lee Revell
2007-09-30 12:29 ` Florian Schmidt
2007-09-30 15:45 ` Florian Schmidt
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=200709291837.51976.mista.tapas@gmx.net \
--to=mista.tapas@gmx.net \
--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®