From: Herman Theron <htheron@hmo.ac.za>
To: buildroot@busybox.net
Subject: [Buildroot] Prelim RTAI integration help needed
Date: Tue, 7 Sep 2010 11:08:14 +0200 (SAST) [thread overview]
Message-ID: <003901cb4e6c$3dd561e0$b98025a0$@ac.za> (raw)
In-Reply-To: <20100907102907.3b8dbe70@surf>
Hi Thomas,
Please let me know if I must send you specific config files, etc to be
able to reproduce the problem.
Thanks
Herman
-----Original Message-----
From: buildroot-bounces@busybox.net [mailto:buildroot-bounces at busybox.net]
On Behalf Of Thomas Petazzoni
Sent: 07 September 2010 10:29 AM
To: buildroot at busybox.net
Subject: Re: [Buildroot] Prelim RTAI integration help needed
Hello,
On Tue, 7 Sep 2010 09:54:02 +0200 (SAST)
"Herman Theron" <htheron@hmo.ac.za> wrote:
> I'm using the internal buildroot toolchain, standard gcc (version
> 4.3.5?) from 2010.08
Ah. Then your problems 2/ and 3/ are quite strange. I'll try to
reproduce them.
> Regarding first compiling the kernel before RTAI: is it possible to
> set the kernel as a dependency for RTAI to ensure that it is build
> before RTAI? Or is the dependencies just for packages?
You can do :
RTAI_DEPENDENCIES = linux26
However, this will make sure than Linux gets build prior to RTAI, but
not that RTAI patches are applied to the kernel.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2010-09-07 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541305813.2396.1283840257891.JavaMail.root@her-mx1>
2010-09-07 6:44 ` [Buildroot] Prelim RTAI integration help needed Herman Theron
2010-09-07 7:37 ` Thomas Petazzoni
2010-09-07 7:54 ` Herman Theron
2010-09-07 8:29 ` Thomas Petazzoni
2010-09-07 9:08 ` Herman Theron [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='003901cb4e6c$3dd561e0$b98025a0$@ac.za' \
--to=htheron@hmo.ac.za \
--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.