From: "Henk Geraads" <linux@hf-electronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Problems building a kernelmodule for OE
Date: Tue, 28 Oct 2008 12:51:30 +0100 [thread overview]
Message-ID: <NGBBLNEOGLJIIJKLFLPFEEAMDKAA.linux@hf-electronics.com> (raw)
In-Reply-To: <NGBBLNEOGLJIIJKLFLPFMEAKDKAA.linux@hf-electronics.com>
Hi Stanislav,
Found the problem with __LINUX_ARM_ARCH__!
the "-march=armv5t" in the makefie compiler line did mess up things!!
the include of the "pxa-regs.h" and "gpio.h" solved the other problem.
Now I've got strange error's from the linker;
make[2]: *** [/home/henk/SystemDev/module/cfi-ktst/cfi-mod.ko] Error 1
make[1]: *** [modules] Error 2
make: *** [default] Error 2
arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/home/armcore/oe/build/tmp/angstrom/staging/arm-angstrom-linux-gnueabi/lib'
arm-angstrom-linux-gnueabi-ld: use the --help option for usage information
make[2]: *** [/home/henk/SystemDev/module/cfi-ktst/cfi-mod.ko] Error 1
make[1]: *** [modules] Error 2
make: *** [default] Error 2
I thought linker option's are very common?
Henk
> -----Oorspronkelijk bericht-----
> Van: Henk Geraads [mailto:linux@hf-electronics.com]
> Verzonden: dinsdag 28 oktober 2008 10:16
> Aan: openembedded-devel@lists.openembedded.org
> Onderwerp: RE: [oe] Problems building a kernelmodule for OE
>
>
> Hi Stanislav
>
> questions,
>
> > -----Oorspronkelijk bericht-----
> > Van: openembedded-devel-bounces@lists.openembedded.org
> > [mailto:openembedded-devel-bounces@lists.openembedded.org]Namens
> > Stanislav Brabec
> > Verzonden: maandag 27 oktober 2008 16:56
> > Aan: openembedded-devel@lists.openembedded.org
> > Onderwerp: Re: [oe] Problems building a kernelmodule for OE
> >
> >
> > Henk Geraads wrote:
> >
> > > when I try to make the module, following error message is produced!
> >
> > It seems, that source code is a bit outdated (intended for older kernel
> > that you have) or you are compiling it in a bad way.
> >
> > > include/linux/calc64.h:25: error: '__LINUX_ARM_ARCH__'
> > undeclared (first use in this function)
> >
> > Strange. It should be defined.
>
> Where should it be defined?
>
> >
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c:67: warning:
> > implicit declaration of function 'GPLR'
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c:67: warning:
> > implicit declaration of function 'GPIO_bit'
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c: In function 'cfi_init':
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c:204: error:
> > 'GPIO_IN' undeclared (first use in this function)
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c:208: error:
> > 'MSC1' undeclared (first use in this function)
> > > /home/henk/cm270/fifodrv/cfi-ktst/cfi-mod.c:209: error:
> > 'GPIO79_nCS_3_MD' undeclared (first use in this function)
> >
> > It indicates that you need to include asm/arch/pxa2xx-regs.h and
> > asm/arch/pxa2xx-gpio.h.
>
> Are these not covered by including "asm/uaccess.h" and "asm/io.h" ?
>
> >
> > --
> > Best Regards / S pozdravem,
> >
> > Stanislav Brabec
> > software developer
> > ---------------------------------------------------------------------
> > SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz
> > Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747
> > 190 00 Praha 9 fax: +420 284 028 951
> > Czech Republic http://www.suse.cz/
> >
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-10-28 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 8:13 Problems building a kernelmodule for OE Henk Geraads
2008-10-27 15:56 ` Stanislav Brabec
2008-10-28 9:15 ` Henk Geraads
2008-10-28 11:51 ` Henk Geraads [this message]
2008-10-28 23:10 ` Stanislav Brabec
2008-10-29 13:46 ` Henk Geraads
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=NGBBLNEOGLJIIJKLFLPFEEAMDKAA.linux@hf-electronics.com \
--to=linux@hf-electronics.com \
--cc=openembedded-devel@lists.openembedded.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