[Xenomai-core] BuildBot progress for sim, tqm860 with RTnet

[Xenomai-core] BuildBot progress for sim, tqm860 with RTnet

[Niklaus Giger]

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?

Best regards

-- 
Niklaus Giger

Re: [Xenomai-core] BuildBot progress for sim, tqm860 with RTnet

[Jan Kiszka]

[-- 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 --]

Re: [Xenomai-core] BuildBot progress for sim, tqm860 with RTnet

[Wolfgang Grandegger]

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).

Looks good.

> 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?

For Xenomai 2.1.x I configure, build and install RTnet as shown:

$ export CROSS_COMPILE=ppc_8xx-
$ ./configure 
--with-linux=/temp/rt/test/linuxppc_2_4_devel-2006_03_26_1343 
--host=ppc-linux --prefix=/root/xeno4rtnet --enable-fec-enet 
--enable-scc-enet
$ make
$ export DESTDIR=/opt/eldk/ppc_8xx
$ make install

Wolfgang.