From: "Henk Geraads" <linux@hf-electronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Problems building a kernelmodule for OE
Date: Wed, 29 Oct 2008 14:46:31 +0100 [thread overview]
Message-ID: <NGBBLNEOGLJIIJKLFLPFOEBADKAA.linux@hf-electronics.com> (raw)
In-Reply-To: <1225235412.9331.13.camel@utx.utx.cz>
Hi Stanislav,
Thanks for the remarks, ideed it seems the .config file was messed up.
I did repopulate the kernel source tree again. Did "make ARCH=arm menuconfig"
Created a new kernel and also did use this new tree to succesfully build my own kernel module.
Best regards,
Henk
> -----Oorspronkelijk bericht-----
> Van: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org]Namens
> Stanislav Brabec
> Verzonden: woensdag 29 oktober 2008 0:10
> Aan: openembedded-devel@lists.openembedded.org
> Onderwerp: Re: [oe] Problems building a kernelmodule for OE
>
>
> Henk Geraads wrote:
>
> > Found the problem with __LINUX_ARM_ARCH__!
> > the "-march=armv5t" in the makefie compiler line did mess up things!!
>
> It is very probably still not correct. When cross compiling the kernel,
> you need to pass "ARCH=arm" to make (and set CPU type in .config.
> Otherwise compile options may be invalid (and you can even corrupt
> your .config file) and then correct -march should be generated by make.
>
> > 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-a
> ngstrom-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?
>
> -Wl is not an option for linker, but cor compiler. Linker should get
> only parameters of -Wl. Additionally -rpath-link is not useful for
> kernel (dynamic linking is an user space issue). Something went wrong
> and make passed bad arguments to the linker.
>
> Here is a make syntax I am using for kernel cross compilation:
> make ARCH=arm CC=arm-angstrom-linux-gnueabi-gcc
> LD=arm-angstrom-linux-gnueabi-ld INSTALL_PATH=$PWD/INSTALL/boot
> INSTALL_MOD_PATH=$PWD/INSTALL
> You may need to add target (e. g. zImage, install, zinstall,
> modules_install).
>
>
> ________________________________________________________________________
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2008-10-29 13:48 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
2008-10-28 23:10 ` Stanislav Brabec
2008-10-29 13:46 ` Henk Geraads [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=NGBBLNEOGLJIIJKLFLPFOEBADKAA.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