Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot(busybox) problem with ccache during rtai-4.0-test2 compiling.
Date: Mon, 10 Feb 2014 18:34:50 +0100	[thread overview]
Message-ID: <52F90DBA.5040706@mind.be> (raw)
In-Reply-To: <CAEqQue1SBkXUggJfRZ_J1x5FmWwSAYxiDoVZhSQpmuqD6b=_Dg@mail.gmail.com>

On 02/09/14 13:12, servo gmrt wrote:
> 2.  My host system is "i686" but i am building linux for "i486", whenever
> i executed the "make linux-menuconfig", buildroot only builds the
> linux-kernel modules, it is not building the rtai modules, while testing
> the new build system and rtai, kernel reports the "unknown symbols in
> rtai modules".
> 
> 3.  Is there any provision in buildroot, to automatically build the RTAI
> modules whenever "make linux-menuconfig" executed ?

 Since I never used RTAI myself, I'm just guessing here, but I guess the
rtai modules are patched directly into the kernel with the rtai patch. In
that case, it's the kernel's build system that takes care of dependency
tracking. Normally the kernel build system is quite good at getting the
dependencies right, but perhaps the rtai people fumbled it. Note, BTW,
that 'make linux-menuconfig' doesn't rebuild anything, you have to do a
'make' again to actually build.

 If the rtai modules are not patched into the kernel but are built as
part of the rtai package, then you have to do an explicit 'make
rtai-rebuild' after the menuconfig. When you do a partial rebuild,
buildroot doesn't try to guess which packages should be rebuilt as well.
This is intentional, because it would be pretty complex to do, and not
guaranteed to be correct anyway.


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-10 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 13:53 [Buildroot] buildroot(busybox) problem with ccache during rtai-4.0-test2 compiling servo gmrt
2014-01-30 19:08 ` Thomas Petazzoni
2014-01-31  5:13   ` servo gmrt
2014-01-31  8:04     ` Thomas Petazzoni
2014-01-31 11:09       ` servo gmrt
2014-02-04  9:08         ` Arnout Vandecappelle
2014-02-08 13:19           ` servo gmrt
2014-02-09 12:12             ` servo gmrt
2014-02-10 17:34               ` Arnout Vandecappelle [this message]
2014-02-10  7:05             ` Arnout Vandecappelle

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=52F90DBA.5040706@mind.be \
    --to=arnout@mind.be \
    --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