All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] building kernel modules
Date: Wed, 11 Nov 2009 11:52:43 -0800	[thread overview]
Message-ID: <4AFB160B.6070001@cs.ucsb.edu> (raw)
In-Reply-To: <20091111005818.GC29442@buzzloop.caiaq.de>

Daniel Mack wrote:
> On Tue, Nov 10, 2009 at 09:18:33AM -0800, Roman Chertov wrote:
>> Turns out it was a division of a long that was causing that.  After I
>> changed the long to a uint32_t then the problem went away.  Now, I have
>> to figure out why I cannot insert the module.
>>
>> musec_can: unknown relocation: 40
>> insmod: can't insert
>> '/proj/tools/can_driver/musec_can/src/musec_can.ko': invalid module format

This was due to a kernel bug
http://lkml.indiana.edu/hypermail/linux/kernel/0903.3/02813.html
The patch provided in the link fixed the problem for me.


>>
>> Modules built during the kernel built work fine.  I guess I have to
>> figure out what linker setting I am missing.
> 
> See dmesg for more of the reason. There's a comprehensive guideline I
> can point you to, just in case that differs from what you did:
> 
>   http://lwn.net/Articles/21823/
> 
>>> After all, what you're seeing is an effect that has to do with your
>>> code, the kernel and gcc. And not with buildroot :)
>> True.  I was just hoping that somebody would give me a starting point as
>>   I new to cross compiling :)  Thanks for the help.
> 
> No problem :)
> 
> Daniel
> 

  reply	other threads:[~2009-11-11 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 21:59 [Buildroot] building kernel modules Roman Chertov
2009-11-09  5:28 ` Roman Chertov
2009-11-09  6:58   ` Daniel Mack
2009-11-09 22:38     ` Roman Chertov
2009-11-09 22:59       ` Daniel Mack
2009-11-10 17:18         ` Roman Chertov
2009-11-11  0:58           ` Daniel Mack
2009-11-11 19:52             ` Roman Chertov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-24 17:00 Brian Beattie

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=4AFB160B.6070001@cs.ucsb.edu \
    --to=rchertov@cs.ucsb.edu \
    --cc=buildroot@busybox.net \
    /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.