All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kuehn <Andreas.Kuehn@gin.de>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2009.11 doesn't build kernel modules
Date: Fri, 12 Feb 2010 11:12:46 +0100	[thread overview]
Message-ID: <4B75299E.8000808@gin.de> (raw)
In-Reply-To: <4B73FE12.6000700@gin.de>

Hi! It's me again.


It seems I kicked myself, for some reasons.

The origin of the problem seems to be the kernel I used. I tried to
build with an 2.6.32.7 kernel and no modules were generated.
Now I used 2.6.32 sources and ... it created modules :-)

Hence, it was not a problem of buildroot, even if I don't know why I
achived various results.


Cheers
	akuehn




Andreas Kuehn wrote:
> Hi All!
> 
> 
> I trying to build an at91sam9263 based system. At earlier versions a
> full compilation run on buildroot creates all pieces including *.ko.
> The current buildroot does not.
> 
> I tried recompiling the kernel and of course make linux26 but no effect.
> Running make linux26-modules created the following output:
> 
> $ make linux26-modules
> cp -dpf
> /usr/cross/GL4200/buildroot-2009.11/output/build/u-boot-2009.06/tools/mkimage
> /usr/cross/GL4200/buildroot-2009.11/output/staging/usr/bin/
> 
> 
> Did I miss something?
> 
> Thanks in advance,
> 	akuehn
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      reply	other threads:[~2010-02-12 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 12:54 [Buildroot] buildroot-2009.11 doesn't build kernel modules Andreas Kuehn
2010-02-12 10:12 ` Andreas Kuehn [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=4B75299E.8000808@gin.de \
    --to=andreas.kuehn@gin.de \
    --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.