All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: niklaus.giger@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] BuildBot progress for sim, tqm860 with RTnet
Date: Thu, 13 Apr 2006 09:28:08 +0200	[thread overview]
Message-ID: <443DFD88.4020000@domain.hid> (raw)
In-Reply-To: <200604130659.23223.niklaus.giger@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

Niklaus Giger wrote:
> Hi
> 
> I was busy improving the buildbot setup and achieved the following:
> - added build slave for simulator
> - added a buildbot for a TQM860L with Denx PPC 2.4 kernel. Cannot yet build 
> the RTnet code.
> - patched buildbot to show names for shell build steps instead of the commands
> - Hacked buildbot to improve the displayed names of the build step
>   (e.g. "configure_xenomai" instead of "configure 2". 
> 
> I will look at Philippe's idea about collecting xenomai statistics later, 
> because it demands more time and effort to implement.
> 
> The following details are probably only of interest for people interested in 
> TQM860 and/or RTnet.
> 
> My setup for the TQM860 was the following:
> - Got Dan Kegel crosstool 0.42
> - Compiled/installed the demo-ppc860 (gcc-3.4.1-glibc-2.3.3)
> - Used linuxppc_2_4_devel-2006-04-06-1735.tar.bz whith a TQM860L_defconfig
>   plus XENOMAI extensions
> - Got RTnet trunk via SVN
> 
> Could the interested parties please comment, whether this is a good 
> combination or whether they prefer something different? If you follow the 
> logs you are able to see each step and configuration option (except building 
> the crosstool).
> 
> configure rtnet fails with the following message:
> checking for 
> RT-extension... /home/buildslave/bin/linuxppc_2_4_devel-2006-04-06-1735 
> (Xenomai 2.0.x)
> checking for Xenomai version... configure: error: *** Unsupported Xenomai 
> version 2.1.50 in /home/buildslave/bin/linuxppc_2_4_devel-2006-04-06-1735
> Is the error correct? Or should I build only against Xenomai 2.0?

No, the trick is to pick the correct --with-arguments - or use
interactive configuration where it is explained that you first have to
decide about the build model (classic like 2.0.x or in-kernel). When
using configure directly (I'm citing --help ;) ):

  --with-rtext=RT-EXTENSION
                          installation path of RTAI or Xenomai 2.0.x
  --with-linux=LINUX      real-time extended Linux kernel
  --with-rtext-config=CONFIG-PATH
                          path of the RT-extension's config tool

So, either use the first switch for 2.0.x or the two others for 2.1 and
above. But the advantage of the make *config path is that RTnet will
leave a .rtnet_config behind which can easily be reused with make oldconfig.

Keep up your great work!

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-04-13  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  4:59 [Xenomai-core] BuildBot progress for sim, tqm860 with RTnet Niklaus Giger
2006-04-13  7:28 ` Jan Kiszka [this message]
2006-04-13  7:28 ` Wolfgang Grandegger

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=443DFD88.4020000@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=niklaus.giger@domain.hid \
    --cc=xenomai@xenomai.org \
    /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.