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: Tue, 04 Feb 2014 10:08:04 +0100	[thread overview]
Message-ID: <52F0ADF4.8080509@mind.be> (raw)
In-Reply-To: <CAEqQue1m_d_ouJMoHqzjyvWawHFry_1C9S39E=1AeyJqFD6R9Q@mail.gmail.com>

On 31/01/14 12:09, servo gmrt wrote:
> I am trying to build integrated linux-kernal, rootfs, and rtai, 
> 
> To complie rtai, I enabled rtai and patch location in .config file. Other
> than that I have not made any changes in any of the buildroot files.
> 
> Is there any changes I should make in buoldroot before buliding RTAI ?

 The RTAI version we have in buildroot is RTAI 3.8.1. So if you are
building RTAI 4.0, it means you are using a fork. So either you have to
contact the maintainer of your fork, or you have to give us the patches
that were applied in order to use RTAI 4.0.

 Regards,
 Arnout

> 
> Thanks & Regards,
> B.Thiyagarajan
> 


-- 
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-04  9:08 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 [this message]
2014-02-08 13:19           ` servo gmrt
2014-02-09 12:12             ` servo gmrt
2014-02-10 17:34               ` Arnout Vandecappelle
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=52F0ADF4.8080509@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