Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] problem with building kernel modules.
Date: Fri, 15 Nov 2013 21:56:54 +0100	[thread overview]
Message-ID: <20131115205654.GH3337@free.fr> (raw)
In-Reply-To: <3FF194268D984DEF96AF81E6681E03E9@JohanW7>

Sagaert, All,

On 2013-11-15 21:24 +0100, Sagaert Johan spake thusly:
> I have a kernel module that I build and install trough the build system.
> This works fine, the module gets build, installed and depmod is run for it.
> 
> The problem occurs if I change the kernel config, the kernel build system
> removes all target/lib/modules/2.6.36.../kernel/* files , including my built modules.
> 
> As a result, my modules are missing.
> 
> How can this be solved ? 

There's no guarantee built into Buildroot that rebuilding a package will
rebuild other packages that depend on it.

The only option for you is to explicitly tell Buildroot to rebuild your
module:
    make fm25clxx-clean-for-reconfigure fm25clxx all

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-11-15 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 20:24 [Buildroot] problem with building kernel modules Sagaert Johan
2013-11-15 20:56 ` Yann E. MORIN [this message]
2013-11-15 23:08   ` Thomas Petazzoni

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=20131115205654.GH3337@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox