[Xenomai-core] Xenomai 2.6.0 in Debian
Hi, thanks for Xenomai 2.6.0! I'm attaching a patch that's helpful for the integration of Xenomai in Debian (and FHS compliant systems in general), moving the architecture dependent test programs from /usr/share to /usr/lib. Thanks in advance, Roland --- xenomai-2.6.0.orig/src/testsuite/regression/xeno-regression-test.in +++ xenomai-2.6.0/src/testsuite/regression/xeno-regression-test.in @@ -46,13 +46,13 @@ echo 0 > /proc/xenomai/latency || : @testdir@/mutex-torture-posix # the tests in this tree -@pkgdir@/regression/posix/leaks -@pkgdir@/regression/posix/shm -@pkgdir@/regression/native/heap -@pkgdir@/regression/native/leaks -@pkgdir@/regression/native/mayday -@pkgdir@/regression/native/tsc -@pkgdir@/regression/native+posix/mq_select +@testdir@/regression/posix/leaks +@testdir@/regression/posix/shm +@testdir@/regression/native/heap +@testdir@/regression/native/leaks +@testdir@/regression/native/mayday +@testdir@/regression/native/tsc +@testdir@/regression/native+posix/mq_select start_load --- xenomai-2.6.0.orig/src/testsuite/regression/native/Makefile.am +++ xenomai-2.6.0/src/testsuite/regression/native/Makefile.am @@ -1,4 +1,4 @@ -tstdir = $(pkgdatadir)/regression/native +tstdir = @XENO_TEST_DIR@/regression/native noinst_HEADERS = check.h --- xenomai-2.6.0.orig/src/testsuite/regression/posix/Makefile.am +++ xenomai-2.6.0/src/testsuite/regression/posix/Makefile.am @@ -1,4 +1,4 @@ -tstdir = $(pkgdatadir)/regression/posix +tstdir = @XENO_TEST_DIR@/regression/posix noinst_HEADERS = check.h --- xenomai-2.6.0.orig/src/testsuite/regression/native+posix/Makefile.am +++ xenomai-2.6.0/src/testsuite/regression/native+posix/Makefile.am @@ -1,4 +1,4 @@ -tstdir = $(pkgdatadir)/regression/native+posix +tstdir = @XENO_TEST_DIR@/regression/native+posix tst_PROGRAMS = mq_select ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [Xenomai-help] Xenomai 2.6.0-rc1
Hi, On 09/06/2011 01:31 PM, Gilles Chanteperdrix wrote: > currently 2.6.0-rc1 fails to build on 2.4 kernel, with errors related to > vfile support. Do we really want to still support 2.4 kernels? No worries here from the Debian (and derivatives) perspective. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Bug#637425: gcc-4.6 issue
Hi, On 08/12/2011 01:18 AM, Gilles Chanteperdrix wrote: > The following patch seems to do the trick. It makes the assumption that > when compiling with -fomit-frame-pointer, we have one more register, so > the "R" constraint will always be able to avoid choosing eax, and eax > will be free for the muxcode, so that the compiler will not choose the > "m" alternative. Thanks for the update! I can confirm that both the patch for xenomai-head and -fno-omit-frame-pointer fix the problem. For Debian's xenomai 2.5.6, I will just use -fno-omit-frame-pointer for now. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] gcc-4.6 issue
Hi, On 08/11/2011 04:48 PM, Daniele Nicolodi wrote: > I compiled linux 2.6.38.8 and xenomai-head with gcc-4.6. The obtained > kernel boots fine but xenomai services do not: latency hangs right after > the sched_setscheduler system call. With the same kernel I compiled user > space with gcc-4.4 and xenomia services work just fine. I can confirm this now for Debian. Sorry for the delay. Will use gcc-4.4 for building the Debian package for now. Attached is a patch you might like to integrate into the GIT repository for the build environment. BTW: You further don't need all the Makefile.in's under revision control when there's also a Makefile.am. Similarly regarding aclocal.m4 and configure. bye, Roland diff --git a/include/nucleus/Makefile.am b/include/nucleus/Makefile.am index 5fc1c21..7af212a 100644 --- a/include/nucleus/Makefile.am +++ b/include/nucleus/Makefile.am @@ -37,4 +37,5 @@ includesub_HEADERS = \ vdso.h \ seqlock.h \ version.h \ - xenomai.h + xenomai.h \ + vfile.h diff --git a/src/skins/common/Makefile.am b/src/skins/common/Makefile.am index 2156165..888bc5b 100644 --- a/src/skins/common/Makefile.am +++ b/src/skins/common/Makefile.am @@ -1,5 +1,7 @@ lib_LTLIBRARIES = libxenomai.la -noinst_HEADERS = sem_heap.h +noinst_HEADERS = \ + sem_heap.h \ + internal.h libxenomai_la_SOURCES = \ assert_context.c \ diff --git a/src/testsuite/xeno-test/Makefile.am b/src/testsuite/xeno-test/Makefile.am index 1d082de..1c8280c 100644 --- a/src/testsuite/xeno-test/Makefile.am +++ b/src/testsuite/xeno-test/Makefile.am @@ -9,4 +9,4 @@ xeno_test_run_CPPFLAGS = -DTESTDIR=\"$(testdir)\" xeno-test: $(srcdir)/xeno-test.in Makefile sed "s,@testdir@,$(testdir)," $< > $@ -EXTRA_DIST = $(test_SCRIPTS) +EXTRA_DIST = $(test_SCRIPTS) xeno-test.in ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] gcc-4.6 issue
Hi, I remember the recent gcc 4.6 issue on this list, but unfortunately, didn't have much time for attention. Now, it found its way to the Debian package: http://bugs.debian.org/637425 I wonder if it is a compiler bug or Xenomai's. Thanks in advance, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] New Debian source package format 3.0
Hi, for some time now, Debian has the new source package version 3.0 [1] to which I'm currently migrating the Xenomai package. This has the following consequences: * I don't need to repackage the upstream tarball anymore, since with the new format, dpkg supports bzip2 besides gz, among others * There are actually 2 different 3.0 package formats: "native" and "quilt". While the former is appropriate for maintaining "Upstream" and Debian together in one single place, the latter is appropriate for Debian packages that have an upstream development location outside Debian. * To migrate appropriately, you can do the following changes in the xenomai.org repository: $ mkdir debian/source $ echo '3.0 (native)' > debian/source/format $ dch 'Switch to dpkg-source 3.0 (native) format' while I will do accordingly at Debian with "native" replaced by "quilt". (Maintaining it as "native" in both locations would only be reasonable if Debian would have official Xenomai release privileges which is neither the case nor necessary. - E.g. maintenance of "old" Xenomai versions in Debian stable while xenomai already has newer versions available.) * You can remove the "-x" Debian revision from the native Debian package and the watch file at xenomai.org. * Debian now ships a ".debian.tar.gz" file instead of ".diff.gz" for the "quilt" version. * Take care of "native" instead of "quilt" when synchronizing with the "downstream" Debian package Thanks for considering. bye, Roland [1] http://wiki.debian.org/Projects/DebSrc3.0 ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [announce] Xenomai v2.5.3
Hi, Gilles Chanteperdrix wrote: > here comes Xenomai v2.5.3, codenamed "Hordes Of Locusts" available from > Xenomai download area: > http://download.gna.org/xenomai/stable/xenomai-2.5.3.tar.bz2 Just uploaded to Debian as xenomai-2.5.3-1. Thanks! bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [PATCH] debian: sync with 2.5.2-2 from debian.org,
On 05/04/2010 08:11 PM, Gilles Chanteperdrix wrote: > What I meant is that we could artificially increment the library ABI > version, so that we get in-line with the package name. Of course, we > pretend we broke the ABI whereas we did not really do it, but it looks > harmless (but is it really?). Just change it for the next ABI changes. No actions really required, currently. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [PATCH] debian: sync with 2.5.2-2 from debian.org,
Hi, On 05/04/2010 09:43 AM, Stefan Kisdaroczi wrote: >> Reading your patch, maybe libxenomai.so.0 should be called libxenomai.so.1 ? > > The comment in the libxenomai1.lintian hunk was added by Roland, so it's > probably > better to ask him. Roland, what do you think ? The comment resulted from the discrepancy between the Debian package name "libxenomai1" and the SO version of libxenomai.so.0. When there was no libxenomai.so, yet, I called the Debian package with all the *.so.* "libxenomai1" by convention. I won't rename it to "libxenomai0" because: (1) I won't downgrade the "version" encoded in the package name (2) There are other SOs in the package which have their own SO versions, even though all or most of them also have "0". I propose keeping number as they are for now. Everything is working fine currently. I just propose to stick to correct library SO versioning. See also http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html which is the Debian perspective on the issue but it gives a good practical introduction to the topic. When SO versions change in the correct way (e.g. major SO version increments on ABI changes), I will update the package version as well. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai in Debian
Hi Stefan, Stefan Kisdaroczi wrote: > I have attached a patch against debian xenomai version 2.5.1-4, changes: > - create group xenomai on install > - added a init-script which sets /sys/.../xenomai_gid if >/sys/.../xenomai_gid exists > - added a modprobe-script that adds the xenomai_gid parameter if the user >did call modprobe without xenomai_gid= > > With this changes, all users which are member of the group xenomai are able > to run xenomai apps, with xeno_nucleus builtin or as a module. Looks fine. Just uploaded into Debian. (And renamed /etc/modprobe.d/xenomai to xenomai.conf.) Thanks! bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [announce] Xenomai v2.5.2
Hi! Gilles Chanteperdrix wrote: > here comes Xenomai v2.5.2, codenamed "Souls Of Distortion" available > from Xenomai download area: > http://download.gna.org/xenomai/stable/xenomai-2.5.2.tar.bz2 Cool, thanks! I'm attaching a patch from Debian. I needed to introduce it because without it, --with-test didn't cause /usr/bin/xeno to access the executables in the specified directory. Thanks for considering! bye, Roland --- xenomai-2.5.2.orig/scripts/xeno.in +++ xenomai-2.5.2/scripts/xeno.in @@ -6,9 +6,6 @@ # e.g. "xeno latency" # -prefix="@prefix@" -exec_prefix="@exec_prefix@" -BINDIR="@bindir@" -unset prefix exec_prefix +XENO_TEST_DIR="@XENO_TEST_DIR@" -exec $BINDIR/$@ +exec $XENO_TEST_DIR/$@ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai in Debian
Hi Gilles, thanks for your mail! And don't worry - there's an updated Xenomai version in Debian sid now thanks to everyone from the Xenomai dev list. Sven put quite some effort into syncing the two projects. If there are any problems, feel free to "bug" me. ;-) Regarding the xenomai-announce list, this sounds like a good idea since many projects have it, including Debian. For me personally, my work much depends on free ressources and Debian release schedule urgency. Btw: The Debian watch system automatically generates an email when xenomai has got a new release. :-) So also no hurry here. See you, bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai in Debian
Hi Gilles, first - I'm sorry if you sometimes feel offended by my work on Xenomai in Debian. I understand that you are very much connected to your project and want to have it working perfectly everywhere. Unfortunately, my time to work on this is limited and the last uploads were work in progress - to provide latest Xenomai in Debian. Further work on it was planned for this weekend. But please also understand that Debian developers will possibly prioritize work on upstream packages where they feel their work is appreciated. So please think about your tone before sending email and driving people away from Xenomai. Gilles Chanteperdrix wrote: > - the package ships with patches for 2.6.24. These I-pipe patches are > outdated and have been publicly announced as being bogus on the Xenomai > mailing lists; Thanks for pointing that out! Will be removed. > - xenomai 2.5.1 seems to have introduced a conflict with sigtest, my > fault, you seem to have fixed this by prefixing all xenomai binaries > with xenomai-, there was a simple solution which would have been for us > to rename only sigtest. First, I was thinking about this solution also, of course. But many of the Xenomai binaries' names are very generic and not easily recognizable as related to Xenomai ("latency", "arith", etc.). (Please consider that there are 1s of binaries in Debian's /usr/bin.) So I decided to rename them all, for consistency. Therefore, also "xenomai-xeno-config". :-) It's one exception. I was completely aware of this and also didn't find it very beautiful. The alternative would have been a separate directory for them, e.g. somewhere under /usr/lib/xenomai. But that would lead to them not being available in user's PATHs. So I decided otherwise. > This looks to me like a bad idea. You are breaking the documented user > interface. Feel free to make suggestions for improvement. > I have already asked publicly for this, but will ask it once again: > please inform the xenomai mailing list of the debian xenomai package > bugs, and get us involved in their resolution. I'm doing this if it concerns you. E.g. your non-PIC bug. Problems with Debian packaging are Debian's task. I'm open to all suggestions, but please CC me, I'm not following the Xenomai list so closely. > Because the debian packaging of xenomai simply do not > meets the quality standards of the Xenomai project. Please stop. Debian sid is the equivalent of a development branch of Xenomai. It's unreleased code. I also don't flame you for bugs in Xenomai but instead send patches. So please let's work friendly each one on his own project and don't flame. Thanks for considering. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Xenomai in Debian
Hi, I'm just working on the Xenomai 2.5.1 Debian package and encountered non-PIC code (evil! ;-) in the shared libraries (skins libraries). You can see it with e.g. $ readelf -d src/skins/native/.libs/libnative.so.3.0.0 The "TEXTREL" tag indicates non-PIC code. $ scanelf -qT src/skins/native/.libs/libnative.so.3.0.0 Shows the function and code offset of the relocation. With $ objdump -d src/skins/native/.libs/libnative.so.3.0.0 I found the actual location of the relocation. I prepared a patch (attached) that fixes it: First, the relocation itself by letting GCC create the address in PIC style. Second, "extern inline" looks a bit counterintuitive at first, but according to the GCC manual, it seems to be what we want (macro behaviour). Thanks Jan for reminding me! bye, Roland --- xenomai-2.5.1.orig/include/asm-x86/syscall.h +++ xenomai-2.5.1/include/asm-x86/syscall.h @@ -161,9 +161,11 @@ ".endif\n\t" ".endm\n\t"); -static inline void __xn_get_eip(void **dest) +__attribute__((always_inline)) +extern inline void __xn_get_eip(void **dest) { -asm volatile("movl $1f, %0; 1:": "=m"(*dest)); +addr: + *dest = &&addr; } static inline void __xn_get_ebp(void **dest) ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai v2.4.4
Roland Stigge wrote: > By the way: lintian(1) detects several empty *.map files which weren't > empty in 2.4.3. i.e. arm_2hal_8c__incl.map blackfin_2hal_8c__incl.map blackfin_2nmi_8c__incl.map generic_2hal_8c__incl.map generic_2nmi_8c__incl.map hal__32_8c__incl.map hal__64_8c__incl.map hal-common_8c__incl.map ia64_2hal_8c__incl.map nmi__32_8c__incl.map powerpc_2hal_8c__incl.map rtdm_8h__incl.map smi_8c__incl.map in doc/generated/html/api/ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai v2.4.4
High, Gilles Chanteperdrix wrote: > A special note for Roland: the configure script now allows configuring > Xenomai on ARM for a "generic" machine, which should be suitable for > generating Debian packages for ARM. Thanks! :-) By the way: lintian(1) detects several empty *.map files which weren't empty in 2.4.3. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package xenomai-2.4.3-4 available
Hi, Gilles Chanteperdrix wrote: > What I criticize is patching without submitting patches upstream, or > without consulting upstream package maintainers, or making debian > patches hard to apply upstream. I both submitted to Xenomai upstream and provided an easy patch (not even assuming the stripped debian/*), you should be fully satisfied now... ;-) For the libssl case, it was basically the same, as I understand it. (I'm not involved into Debian's openssl packaging, though.) > For instance I saw there was a bug with generating debian packages > for ARM. Instead of reporting this bug upstream, which, as the > maintainer of Xenomai ARM port, I could have helped to resolve, you > chose to resolve the bug silently [...] I just incorporated the patch by Riku Voipio for Debian #477720 which resolved the problem for Debian's ARM porters. (Further, I sent you the patch in a convenient way...) If you have further improvements in 2.4.4, fine. :-) bye, Roland PS: I hope it doesn't look to the others like we are complaining about each other's work. So for the rest of xenomai-core developers: This is just mine and Gilles' way to say "thanks for your work" to each other. ;-))) ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package xenomai-2.4.3-4 available
Hi, Gilles Chanteperdrix wrote: > the way Debian maintained a patch to the ssh package is the > reason why a bug could remain unnoticed during two years in Debian > distributions, including so-called "stable" distributions. So, maybe it > is time for a change. First, it doesn't matter most how you maintain a patch. Most important is that sufficient code review is done, which unfortunately didn't happen in the libssl case. Second, the actual libssl patch in .diff.gz was the following: === diff -u openssl-0.9.8g/crypto/rand/md_rand.c openssl-0.9.8g/crypto/rand/md_rand.c --- openssl-0.9.8g/crypto/rand/md_rand.c +++ openssl-0.9.8g/crypto/rand/md_rand.c @@ -271,7 +271,10 @@ else MD_Update(&m,&(state[st_idx]),j); +/* + * Don't add uninitialised data. MD_Update(&m,buf,j); +*/ MD_Update(&m,(unsigned char *)&(md_c[0]),sizeof(md_c)); MD_Final(&m,local_md); md_c[1]++; === I.e. quite clear in my opinion. It wouldn't be if Debian wouldn't ship .diff.gz separately. (The above patch was actually reported upstream and there was no objection.) Third, the above case is different from our case: While I consider debian/* as Debian specific, the above patch was not Debian specific (it was actually introduced to ease valgrind usage). Therefore, I even consider the libssl patch style (not the semantics! :-) ) above as good; but patching debian/* in Debian's diff.gz as bad. Fourth, you are proposing the same patching technique as above (which you criticize as not appropriate). > But of course, if you insist, this probably can be worked around by > writing some merging script. Yeah, maybe this is the way to go. Easy to implement and minimizes the work for all participants. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package xenomai-2.4.3-4 available
Hi, Gilles Chanteperdrix wrote: > Shipping the xenomai tarball with the debian directory has a real added > value: it allows people to build debian package without anything else, > this is an unofficial package, of course, but it can be built before the > Debian patch is generated. Well, for people who catch the package within the few hours between Xenomai release and the Debian version of it. ;-) > IMO, it would make your life easier if you considered the debian > directory part of the Xenomai package, and start working from this > directory. If you ask for it, we can probably even give you write > access to the repository, so that the debian packaging effort is fully > integrated to Xenomai. As discussed earlier this year: Every Debian package is a (small) fork of the respective "upstream" release, with own Debian release numbers between upstream releases, e.g. 2.4.4-1 and 2.4.4-2. Maintaining this at xenomai.org would require branches on every (minor) Xenomai release, e.g. 2.4.3 and 2.4.4 (besides me having repository write access), because Debian revisions usually come out more often than "upstream" versions (as you have seen 2.4.3-1 ... 2.4.3-7). Therefore, I prefer maintaining it at Debian like most other packages. We already have "trunk" and the stable release branches at xenomai.org. The above would require an additional level of branching, maintenance and synchronization work. Another solution at Debian is called "native" packages where Debian revisions and upstream versions are synchronized (i.e. no separate Debian revisions). The problem here is that at every point in time, Debian can decide to do a new revision (e.g. within a few hours on security fixes) which may not be in the interest of other xenomai maintainers. E.g. this way, Debian would decide when 2.4.5 and 2.4.6 (or 2.4.4.1 and 2.4.4.2?) will be released. This doesn't scale well with the number of Linux distros. ;) For non-native packages in Debian (as Xenomai is currently), the debian/ directory is separated out into the .diff.gz patch which is good for seeing how e.g. debian/rules looks like. If I would take the current "upstream" tarball and only patch debian/rules in the diff.gz, the resulting contents of the file is no recognizable from the patch alone. Therefore, this is not common practice in Debian. Further, it's not only me who works on Debian packages. Sometimes, when I'm not available, one of the other 1000 Debian developers will do Debian adjustments to the xenomai package in Debian. I guess you don't want to give all of them write access to xenomai.org. ;) So you have the choice between the following possibilities: 1) Leave the process as it is (Debian using the upstream tarball, stripped from debian/*, and adding an own debian/* in a separately shipped patch) 2) Give me (and maybe Debian as a whole) write access to Xenomai.org and the right to branch at every "normal" Xenomai release, doing Debian revisions. Problem here: Additional work for Debian because not only Debian revisions must be done but also synchronization to the v2.4.x (stable) brach and trunk. (I.e. changes are most often in 3 places) 3) Give me (and maybe Debian as a whole) write access to Xenomai.org and the right to do xenomai releases whenever Debian wants (i.e. "native" Debian package) I guess you prefer (1)? ;-) bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package xenomai-2.4.3-4 available
Hi, Gilles Chanteperdrix wrote: > > So feel free to do a 2.4.4 (or whatever) release soon. :-) > > > > (For integrating the Debian changes in addition to the respective > > upstream changes, just remove the man pages in debian/, > > debian/xenomai-runtime.manpages and the /bin/bash patch.) > > I would have felt more comfortable if you could have done it (and more > importantly test it). Besides, the 2.4.4 release is coming, and I would > have liked to release it with all the changes that you made. I'm attaching a patch that I would apply to branches/v2.4.x if it would be considered as 2.4.4. Please note that on integrating Xenomai 2.4.4 (or whatever) upstream in Debian, I will strip debian/* from the original tarball to separate the Debian part from "upstream". For the same reason, please consider to remove it from the tarball. (It can stay in SVN, though.) bye, Roland diff -ruN xenomai-2.4.x/configure.in debian/xenomai-2.4.4/configure.in --- xenomai-2.4.x/configure.in 2008-05-26 13:23:26.0 +0200 +++ debian/xenomai-2.4.4/configure.in 2008-05-26 11:55:24.0 +0200 @@ -799,6 +799,17 @@ doc/Makefile \ doc/txt/Makefile \ doc/man/Makefile \ + doc/man/clocktest.man \ + doc/man/cyclictest.man \ + doc/man/irqbench.man \ + doc/man/irqloop.man \ + doc/man/klatency.man \ + doc/man/latency.man \ + doc/man/rtcanconfig.man \ + doc/man/rtcanrecv.man \ + doc/man/rtcansend.man \ + doc/man/switchbench.man \ + doc/man/switchtest.man \ doc/man/runinfo.man \ doc/man/xeno-config.man \ doc/man/xeno-info.man \ diff -ruN xenomai-2.4.x/debian/changelog debian/xenomai-2.4.4/debian/changelog --- xenomai-2.4.x/debian/changelog 2008-05-26 10:52:55.0 +0200 +++ debian/xenomai-2.4.4/debian/changelog 2008-05-26 12:32:42.0 +0200 @@ -1,3 +1,63 @@ +xenomai (2.4.4-1) unstable; urgency=low + + * New upstream release + + -- Roland Stigge <[EMAIL PROTECTED]> Mon, 26 May 2008 11:58:30 +0200 + +xenomai (2.4.3-7) unstable; urgency=low + + * Included patch from Riku Voipio to fix ARM compile issues +(Closes: #477720) + + -- Roland Stigge <[EMAIL PROTECTED]> Thu, 24 Apr 2008 23:18:01 +0200 + +xenomai (2.4.3-6) unstable; urgency=low + + * Added lintian override for recursive include directories (necessary +according to upstream) + * Added missing man pages (can be removed when integrated upstream) + * debian/rules: Fixed klatency/run script to be proper shell script + + -- Roland Stigge <[EMAIL PROTECTED]> Tue, 22 Apr 2008 12:23:22 +0200 + +xenomai (2.4.3-5) unstable; urgency=low + + * Install xeno-config into libxenomai-dev where the executable is + + -- Roland Stigge <[EMAIL PROTECTED]> Sat, 19 Apr 2008 22:15:07 +0200 + +xenomai (2.4.3-4) unstable; urgency=low + + * Move /usr/lib/xenomai to original upstream /usr/share/xenomai + + -- Roland Stigge <[EMAIL PROTECTED]> Fri, 18 Apr 2008 19:51:49 +0200 + +xenomai (2.4.3-3) unstable; urgency=low + + * debian/rules: Separated prepare-patch.sh calls for individual +architectures (Closes: #473098) + + -- Roland Stigge <[EMAIL PROTECTED]> Thu, 10 Apr 2008 10:01:33 +0200 + +xenomai (2.4.3-2) unstable; urgency=low + + * Enable x86 patches for both i386 and amd64 (Closes: #473098) + + -- Roland Stigge <[EMAIL PROTECTED]> Tue, 01 Apr 2008 10:04:51 +0200 + +xenomai (2.4.3-1) unstable; urgency=low + + * New upstream release + * Added debian/watch + + -- Roland Stigge <[EMAIL PROTECTED]> Tue, 25 Mar 2008 14:13:50 +0100 + +xenomai (2.4.2-3) unstable; urgency=low + + * Fixed bashisms by using "#!/bin/bash" (Closes: #471871) + + -- Roland Stigge <[EMAIL PROTECTED]> Sat, 22 Mar 2008 17:01:11 +0100 + xenomai (2.4.2-2) unstable; urgency=low * debian/copyright: Refined Copyrights diff -ruN xenomai-2.4.x/debian/control debian/xenomai-2.4.4/debian/control --- xenomai-2.4.x/debian/control 2008-05-26 10:52:55.0 +0200 +++ debian/xenomai-2.4.4/debian/control 2008-05-26 11:58:29.0 +0200 @@ -8,7 +8,7 @@ Package: xenomai-runtime Section: devel -Architecture: amd64 arm i386 ia64 powerpc +Architecture: amd64 arm armeb armel i386 ia64 powerpc Depends: ${shlibs:Depends} Suggests: linux-patch-xenomai, xenomai-doc Replaces: xenomai @@ -47,7 +47,7 @@ Package: libxenomai1 Section: libs -Architecture: amd64 arm i386 ia64 powerpc +Architecture: amd64 arm armeb armel i386 ia64 powerpc Depends: ${shlibs:Depends} Suggests: linux-patch-xenomai, xenomai-doc Replaces: xenomai @@ -64,7 +64,7 @@ Package: libxenomai-dev Section: libdevel -Architecture: amd64 arm i386 ia64 powerpc +Architecture: amd64 arm armeb armel i386 ia64 powerpc Depends: libxenomai1 (= ${binary:Version}) Suggests: linux-patch-xenomai, xenomai-doc Replaces: xenomai diff -ruN xenomai-2.4.x/debian/libxenomai1.lintian debian/xenomai-2.4.4/debian/libxenomai1.lintian --- xenomai-2.4.x/debian/libxenomai1.lintian 2008-05-26 10:52:55.00
Re: [Xenomai-core] Debian package xenomai-2.4.3-4 available
Hi Gilles, thanks for your response. ;-))) Gilles Chanteperdrix wrote: > I am trying to merge the debian changes back into Xenomai, however, I > have two problems: > - I can not find back the 2.4.3-4 patch, I only find 2.4.3-7; No problem - always just take the latest one, currently 2.4.3-7. > - I do not want to merge changes that replace /bin/sh with /bin/bash > since we fixed the bashism the right way (it is important for people > of the embedded world, that Xenomai does not require /bin/bash, since > embedded boxes may use other shells); > - I do not want to include the manual pages in the debian/ > sub-directory since I merged your patch adding manual pages to the > proper place. Fine. Just do the changes the way you like it Xenomai ("upstream"): Bashism fixes and man pages in the proper upstream place. On next merge from Xenomai (e.g. 2.4.4 to Debian 2.4.4-1), I will synchronize it from xenomai.org. For 2.4.3, the respective change would require maintainer script regeneration due to changes in Makefile.am's, which I would like to prevent. So feel free to do a 2.4.4 (or whatever) release soon. :-) (For integrating the Debian changes in addition to the respective upstream changes, just remove the man pages in debian/, debian/xenomai-runtime.manpages and the /bin/bash patch.) bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] warning: symlink-is-self-recursive
Hi, Roland Stigge wrote: > = > W: libxenomai-dev: symlink-is-self-recursive > usr/include/xenomai/asm-generic/xenomai . > N: > N: The symbolic link is recursive to a higher directory of the symlink > N: itself. This means, that you can infinitely chdir with this symlink. > N: This is usually not okay, but sometimes wanted behaviour. > N: > W: libxenomai-dev: symlink-is-self-recursive > usr/include/xenomai/asm-sim/asm . > W: libxenomai-dev: symlink-is-self-recursive > usr/include/xenomai/asm-sim/xenomai . > W: libxenomai-dev: symlink-is-self-recursive > usr/include/xenomai/asm-x86/xenomai . > W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/xenomai . > = > > I.e. installing Xenomai created those recursive links which might be > there for source compatibility reasons. Can they be removed at some > point or should I accept the above issue as intended for the future? No comment from anyone? Maybe I should detect the necessity for those links by removing and seeing if anyone complains? ;-) bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Missing manual pages
Hi, Jan Kiszka wrote: > While nitpicking can sometimes be useful, though... Thanks for the comments, I'm attaching the patch that integrates the updated version of the man pages (incl. Makefile.am). bye, Roland diff -ruN xenomai-2.4.3.orig/doc/man/clocktest.man.in xenomai-2.4.3/doc/man/clocktest.man.in --- xenomai-2.4.3.orig/doc/man/clocktest.man.in 1970-01-01 01:00:00.0 +0100 +++ xenomai-2.4.3/doc/man/clocktest.man.in 2008-04-20 00:03:48.0 +0200 @@ -0,0 +1,36 @@ +'\" t +.\" ** The above line should force tbl to be a preprocessor ** +.\" Man page for clocktest +.\" +.\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> +.\" +.\" You may distribute under the terms of the GNU General Public +.\" License as specified in the file COPYING that comes with the +.\" Xenomai distribution. +.\" +.pc +.TH CLOCKTEST 1 "2008-04-01" "@PACKAGE_VERSION@" "Xenomai" +.SH NAME +clocktest \- Xenomai Clock Test +.SH SYNOPSIS +.\" The general command line +.B clocktest +.SH DESCRIPTION +\fBclocktest\fP is part of the Xenomai test suite and tests the Clock. For each +CPU, it repeatedly prints a time offset (compared to the reference +gettimeofday()), a drift value, the number of warps and the maximum warp in +microseconds. + +For this program to work, you need to run a suitable Xenomai enabled kernel +with the respective module (xeno_posix). +.SH OPTIONS +\fBclocktest\fP accepts the following options: +.TP +.B \-C +tested clock, default=0 (CLOCK_REALTIME) +.TP +.B \-T +default=0, so ^C to end +.SH AUTHOR +\fBclocktest\fP was written by Jan Kiszka <[EMAIL PROTECTED]>. This man page +was written by Roland Stigge <[EMAIL PROTECTED]>. diff -ruN xenomai-2.4.3.orig/doc/man/cyclictest.man.in xenomai-2.4.3/doc/man/cyclictest.man.in --- xenomai-2.4.3.orig/doc/man/cyclictest.man.in 1970-01-01 01:00:00.0 +0100 +++ xenomai-2.4.3/doc/man/cyclictest.man.in 2008-04-20 00:03:48.0 +0200 @@ -0,0 +1,70 @@ +'\" t +.\" ** The above line should force tbl to be a preprocessor ** +.\" Man page for cyclictest +.\" +.\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> +.\" +.\" You may distribute under the terms of the GNU General Public +.\" License as specified in the file COPYING that comes with the +.\" Xenomai distribution. +.\" +.pc +.TH CYCLICTEST 1 "2008-04-01" "@PACKAGE_VERSION@" "Xenomai" +.SH NAME +cyclictest \- Xenomai high resolution timer test +.SH SYNOPSIS +.\" The general command line +.B cyclictest +.RI [ options ] +.SH DESCRIPTION +\fBcyclictest\fP is part of the Xenomai test suite and tests the POSIX skin of Xenomai with a cyclic timer test. + +For this program to work, you need to run a suitable Xenomai enabled kernel with the respective module (xeno_posix). +.SH OPTIONS +\fBcyclictest\fP accepts the following options: +.TP +.B \-b USEC, \-\-breaktrace=USEC +send break trace command when latency > USEC +.TP +.B \-c CLOCK, \-\-clock=CLOCK +select clock: +.RS 1.5i +0 = CLOCK_MONOTONIC (default) +.P +1 = CLOCK_REALTIME +.RE +.TP +.B \-d DIST, \-\-distance=DIST +distance of thread intervals in us default=500 +.TP +.B \-i INTV, \-\-interval=INTV +base interval of thread in us default=1000 +.TP +.B \-l LOOPS, \-\-loops=LOOPS +number of loops: default=0 (endless) +.TP +.B \-n, \-\-nanosleep +use clock_nanosleep +.TP +.B \-p PRIO, \-\-prio=PRIO +priority of highest prio thread +.TP +.B \-q, \-\-quiet +print only a summary on exit +.TP +.B \-r, \-\-relative +use relative timer instead of absolute +.\".TP +.\".B \-s, \-\-system +.\"use sys_nanosleep and sys_setitimer +.TP +.B \-t NUM, \-\-threads=NUM +number of threads: default=1 +.TP +.B \-v, \-\-verbose +output values on stdout for statistics + +format: n:c:v n=tasknum c=count v=value in us +.SH AUTHOR +\fBcyclictest\fP was written by Thomas Gleixner <[EMAIL PROTECTED]>. This man page +was written by Roland Stigge <[EMAIL PROTECTED]>. diff -ruN xenomai-2.4.3.orig/doc/man/irqbench.man.in xenomai-2.4.3/doc/man/irqbench.man.in --- xenomai-2.4.3.orig/doc/man/irqbench.man.in 1970-01-01 01:00:00.00000 +0100 +++ xenomai-2.4.3/doc/man/irqbench.man.in 2008-04-20 00:03:48.0 +0200 @@ -0,0 +1,46 @@ +'\" t +.\" ** The above line should force tbl to be a preprocessor ** +.\" Man page for irqbench +.\" +.\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> +.\" +.\" You may distribute under the terms of the GNU General Public +.\" License as specified in the file COPYING that comes with the +.\" Xenomai distribution. +.\" +.pc +.TH IRQBENCH 1 "2008-04-19" "@PACKAGE_VERSION@" "Xenomai" +.SH NAME +irqbench \- Xenomai IRQ benchmark, host control +.SH SYNOPSIS +.\" The general command line +.B irqbench +.RI [ opt
[Xenomai-core] Debian lintian warning: symlink-is-self-recursive
Hi, Debian's lintian(1), the package checker, tells me: = W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/asm-generic/xenomai . N: N: The symbolic link is recursive to a higher directory of the symlink N: itself. This means, that you can infinitely chdir with this symlink. N: This is usually not okay, but sometimes wanted behaviour. N: W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/asm-sim/asm . W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/asm-sim/xenomai . W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/asm-x86/xenomai . W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/xenomai . = I.e. installing Xenomai created those recursive links which might be there for source compatibility reasons. Can they be removed at some point or should I accept the above issue as intended for the future? Thanks, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Missing manual pages
Hi, recently, a Xenomai developer in Munich remarked that Debian developers are sometimes nitpickers. Right. Debian requires a man page for every executable. Therefore, I wrote the remaining ones. Attached are the following files: clocktest.man.in cyclictest.man.in irqbench.man.in irqloop.man.in klatency.man.in latency.man.in rtcanconfig.man.in rtcanrecv.man.in rtcansend.man.in switchbench.man.in switchtest.man.in Feel free to integrate them and correct/extend them where I was missing enough insight. Thanks, Roland '\" t .\" ** The above line should force tbl to be a preprocessor ** .\" Man page for clocktest .\" .\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> .\" .\" You may distribute under the terms of the GNU General Public .\" License as specified in the file COPYING that comes with the .\" Xenomai distribution. .\" .pc .TH CLOCKTEST 1 "2008-04-01" "@PACKAGE_VERSION@" "Xenomai" .SH NAME clocktest \- Xenomai Clock Test .SH SYNOPSIS .\" The general command line .B clocktest .SH DESCRIPTION \fBclocktest\fP is part of the Xenomai test suite and tests the Clock. For each CPU, it repeatedly prints a time offset (compared to the reference gettimeofday()), a drift value, the number of warps and the maximum warp in microseconds. For this program to work, you need to run a suitable Xenomai enabled kernel with the respective module (xeno_posix). .SH AUTHOR \fBclocktest\fP was written by Jan Kiszka <[EMAIL PROTECTED]>. This man page was written by Roland Stigge <[EMAIL PROTECTED]>. '\" t .\" ** The above line should force tbl to be a preprocessor ** .\" Man page for cyclictest .\" .\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> .\" .\" You may distribute under the terms of the GNU General Public .\" License as specified in the file COPYING that comes with the .\" Xenomai distribution. .\" .pc .TH CLOCKTEST 1 "2008-04-01" "@PACKAGE_VERSION@" "Xenomai" .SH NAME cyclictest \- Xenomai high resolution timer test .SH SYNOPSIS .\" The general command line .B cyclictest .RI [ options ] .SH DESCRIPTION \fBcyclictest\fP is part of the Xenomai test suite and tests the POSIX skin of Xenomai with a cyclic timer test. For this program to work, you need to run a suitable Xenomai enabled kernel with the respective module (xeno_posix). .SH OPTIONS \fBcyclictest\fP accepts the following options: .TP .B \-b USEC, \-\-breaktrace=USEC send break trace command when latency > USEC .TP .B \-c CLOCK, \-\-clock=CLOCK select clock: .RS 1.5i 0 = CLOCK_MONOTONIC (default) .P 1 = CLOCK_REALTIME .RE .TP .B \-d DIST, \-\-distance=DIST distance of thread intervals in us default=500 .TP .B \-i INTV, \-\-interval=INTV base interval of thread in us default=1000 .TP .B \-l LOOPS, \-\-loops=LOOPS number of loops: default=0 (endless) .TP .B \-n, \-\-nanosleep use clock_nanosleep .TP .B \-p PRIO, \-\-prio=PRIO priority of highest prio thread .TP .B \-q, \-\-quiet print only a summary on exit .TP .B \-r, \-\-relative use relative timer instead of absolute .\".TP .\".B \-s, \-\-system .\"use sys_nanosleep and sys_setitimer .TP .B \-t NUM, \-\-threads=NUM number of threads: default=1 .TP .B \-v, \-\-verbose output values on stdout for statistics format: n:c:v n=tasknum c=count v=value in us .SH AUTHOR \fBcyclictest\fP was written by Thomas Gleixner <[EMAIL PROTECTED]>. This man page was written by Roland Stigge <[EMAIL PROTECTED]>. '\" t .\" ** The above line should force tbl to be a preprocessor ** .\" Man page for irqbench .\" .\" Copyright (C) 2008 Roland Stigge <[EMAIL PROTECTED]> .\" .\" You may distribute under the terms of the GNU General Public .\" License as specified in the file COPYING that comes with the .\" Xenomai distribution. .\" .pc .TH IRQBENCH 1 "2008-04-19" "@PACKAGE_VERSION@" "Xenomai" .SH NAME irqbench \- Xenomai IRQ benchmark, host control .SH SYNOPSIS .\" The general command line .B irqbench .RI [ options ] .SH DESCRIPTION \fBirqbench\fP is part of the Xenomai test suite and benchmarks IRQs. It is the controlling part running on a plain Linux host, connected via RS232 or Laplink with the target which is running a suitable Xenomai enabled kernel with the respective module (xeno_posix). The target must run \fBirqloop\fP (1). .SH OPTIONS \fBirqbench\fP accepts the following options: .TP .B \-p signal period, default=100 us .TP .B \-T default=0, so ^C to end .TP .B \-o 0=serial (default), 1=parallel .TP .B \-a default=0x3f8/0x378 .TP .B \-f freeze trace for each new max latency .SH "SEE ALSO" .BR /usr/share/doc/xenomai-doc/txt/irqbench.txt, .BR irqloop (1) .SH AUTHOR \fBirqbench\fP was written by Jan Kiszka <[EMAIL PROTECTED]>. This man page was written by Ro
[Xenomai-core] klatency run script
Hi, for the creation of the run script for klatency, I propose the attached change to make it a proper executable (script). Thanks for considering, Roland --- src/testsuite/klatency/Makefile.am.orig 2008-04-19 21:33:42.0 +0200 +++ src/testsuite/klatency/Makefile.am 2008-04-19 21:34:16.0 +0200 @@ -13,7 +13,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Debian package xenomai-2.4.3-4 available
[Warning: First in a series of several issues applicable to xenomai.org's code.] Hi, at http://packages.qa.debian.org/x/xenomai.html, you can find the latest version of Debian's package "xenomai". The "diff" to xenomai 2.4.3 applies to the normal Xenomai distribution with an empty debian/ directory. Feel free to synchronize the Debian changes back to the mainline Xenomai repository, especially the Debian packaging has been fixed. Thanks, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai/SOLO - RTOS emulation for standard Linux
Wolfgang Denk wrote: > If it comes to hard, reliable real-time behaviour, we recommend > Xenomai/ipipe to all our customers. However, there are some who think > it is important to have an "original, unpatched" kernel.org source > tree. These obviously run for PREEMPT_RT, and SOLO. Please remember that PREEMPT_RT currently doesn't mean "unpatched", so you could theoretically patch every PREEMPT_RT enhanced kernel with ipipe instead... ;-> (Feelings of customers are a completely different thing, though...) Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai/SOLO - RTOS emulation for standard Linux
Hi, Wolfgang Denk wrote: >> Is it worth providing a separate xenomai-solo package in Debian right >> now (considering it being propagated to Debian 5.0 and supported there >> in this form until ca. 2010), or should we wait until Xenomai/SOLO is >> integrated into Xenomai mainline? > > Integration into Xenomai mainline means waiting for Xenomai 3, which > seems still a pretty long way to go. > > On the other hand, you need a PREEMPT_RT enhanced Linux kernel for > Xenomai/SOLO to provide real-time behaviour which is probably needed > in most cases when you try and emulate a RTOS. This is probably a > bigger hurdle? I think an RT-patched kernel is quite common, at least if I consider the realtime conscious Debian user community. For other realtime applications such as JACK (though in a completely different application domain), the respective kernels are also often presumed. So if we are talking about Xenomai 3 in the order of years, Xenomai/SOLO as a separate package seems worth considering if it matures reasonably. The other "desktop suitable" approach is the simulator. Both Xenomai/SOLO and the simulator are good candidates for inclusion in the OS distribution since (apart from certain kernel requirements) they can be provided as universal binary packages in userspace. The problem with xenosim is its dependency upon gcc-2.95.6 sources. Since Debian packages must provide the complete sources for building the binary packages or alternatively/additionally have build dependencies satisfied by other (binary) Debian packages in the distribution, this is not an easy task (without gcc 2.95.x being in Debian anymore). One way to go could be utilizing a newer GCC (4.x) instead of 2.95.x, but that doesn't work with current xenosim. Is it worth it to put porting effort into this spot? Thanks! bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai/SOLO - RTOS emulation for standard Linux
Hi, Wolfgang Denk wrote: > DENX Software Engineering is proud to announce Xenomai/SOLO, the new > RTOS emulator that runs as a normal user-space application on a > standard Linux kernel. Of course, when timing requirements have to be > met, a real-time capable Linux kernel with the PREEMPT_RT support > enabled should be used. Thanks very much for this package! Is it worth providing a separate xenomai-solo package in Debian right now (considering it being propagated to Debian 5.0 and supported there in this form until ca. 2010), or should we wait until Xenomai/SOLO is integrated into Xenomai mainline? bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [Fwd: Bug#471871: xenomai-runtime: bashism in /bin/sh script]
Jan Kiszka wrote: > Maybe someone with idle cycles left could have a look at this. Idle? Preempted, at most! Attached is what I will apply to the Debian version. Feel free to do as well... bye, Roland diff -u scripts.orig/xeno-info scripts/xeno-info --- scripts.orig/xeno-info 2007-12-09 11:46:37.0 +0100 +++ scripts/xeno-info 2008-03-22 16:50:19.0 +0100 @@ -1,4 +1,4 @@ -#! /bin/sh +#! /bin/bash # # This file has been lifted 'as is' from linux/scripts/ver_linux. # Adapted to be run also under the BusyBox. If you want to test it under the BusyBox use diff -u scripts.orig/xeno-load.in scripts/xeno-load.in --- scripts.orig/xeno-load.in 2007-12-09 11:46:37.0 +0100 +++ scripts/xeno-load.in 2008-03-22 16:50:57.0 +0100 @@ -1,4 +1,4 @@ -#! /bin/sh +#! /bin/bash # Xenomai application loader script. # (Processes the .runinfo files) # June 2004, <[EMAIL PROTECTED]> diff -u scripts.orig/xeno-test.in scripts/xeno-test.in --- scripts.orig/xeno-test.in 2008-02-20 18:18:46.0 +0100 +++ scripts/xeno-test.in 2008-03-22 16:50:32.0 +0100 @@ -1,4 +1,4 @@ -#! /bin/sh +#! /bin/bash # Adapted to be run also under the BusyBox. # If you want to test it this way, do: sh xeno-test ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Wiki update: Debian package
Hi, I just updated the information on the Debian package page at http://xenomai.org/index.php/Building_Debian_packages . For corrections for this page and the Debian package, feel free to contact me. Thanks, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Script marking
Hi, Gilles Chanteperdrix wrote: > I see that xenomai packages depends on glibc version >= 2.7.1. Is this > dependency really needed ? Without this dependency it would be > possible to compile the Xenomai package for older versions of Debian. This is an automatically generated dependency at package built time _only_ for Debian sid (to be released later), and only for the binary package. If you build the package for yourself, or in another Debian environment (an already released version, e.g. for backporting?), the dependency would look different. Theoretically, it could even be sth. else than glibc. ;-O The versioned dependency is for safety reasons, not always really necessary, but provided be default; taken from the actual build environment... bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Script marking
Gilles Chanteperdrix wrote: >> Further, I updated the package in Debian with the suggested changes. > > We trust you, please send patches. The attached patch (and the latest version of it) can also always be found at the Debian developer's package page for Xenomai at http://packages.qa.debian.org/x/xenomai.html . It applies to the latest Xenomai release (currently 2.4.2), and assumes that there is _no_ debian/ directory in the original source tree (as discussed beforehand - Debian maintains the complete debian/* hierarchy completely - for further questions just ask). bye, Roland õÇGì\íWÛF³ÿÿSãS^lÉ:¡HÂ-&ϹÜYZÛ*²¤j%mó¿ßÙ]½Ø2¤ îsOIð´;;;û×]aYÜ08¾µa?µ7ì(ñG]é&~Ê.ݲR!SÛív»Ú¶¾ÙÎX?>ïlnA[¿ïì4þ-ýÝÕ°öOúôaÝÇóÖx'Ñ(q&à7ë¤~þDm.ÆÌ-9²ÀEâ¤"Çtì¤àKpbl'>Þ îÀ'ôüpÔ°²8 Á³OEd8Å6¸ñ]DêÚ4ÔajFpÁ4J®a:!³tlN¢DÐh!D¡+:[EMAIL PROTECTED]"V" Î YüP8 ~X>vàVÖ¦~ea ;8^åÁwqHäo>r;ÓPÌ©#¯C?çL4_1AÍ\I%¾¹88{ÇĸZ´©?Áet&1¤3ei¥0ô:AÈ÷ ºÉ4ñS Je!³ Ly3_²ÝhB2^î '¾;$C®õE!«ïéTPIË¢ü:KW*tï&5ã'û'8/^^ewìãüQº±HébyÔÀ5 Y&ѤaI;©zÑ´Qlè¾i¼F&o;°ì! ávAÑ{ض½Ü°x¥ÄÓå}§ûé W2$ÔIRv×BÄ9 qZ¯ýQ°à;æVÏó½PÍ ³ îl½tï2¦BÒÆAFß !?Î5ð6ü;Ê`âÒ1±FáB4"âp#fÓ ñúF¤ºôbÚìF{ ÿ+äj%·z½l/}bòh¢í¥¯ÑMÿñ´ÉáÿoTÐöR2éGÑQ FI ÿJO `¾ESÛK ªí¥GÑÕöÒßQV³ßª®¨C_Éí~×øawàÈqNw/ÞnÛý½7¬z÷ïï]7ïðë8qýsMÈí÷:=h¯w67Èã·/Ƹt±ã^;#\+GêãÿâDm9u² ö¢ üråîB9¡Ñ8 ûpáÀ&¬oô{=xóî6z½m"NÅ8É8Y:H6¼:Y,SDÓ$¹8E$ùq,àH²Möç°²·Jd×;ø²A/ôò^Ñ˽ü@/ÏgÁË$ìhÁ0ãv ág°?ñSäs×s&_GðÒã+¶c®ìB`£¦ý´µ:®ÃR [EMAIL PROTECTED])Íþ-ãϾüãÚ¿9¡}Íw¦b`{¢®ó|áÈA ¾Ib4¢evFùW=»Fûíu(E>!ÎÖ(PWQ³°}oN -Dµ²¯£=EûøÄI|ÒÔ£#lÜhçíu û7w8ëT48)éÞ-Z7ÇïqEÉp ÐLÂÍF£í([EMAIL PROTECTED]¹#YçFûS7IWå.ÙÔ(´ô¤eg`m,³Nß×ìÛÙëhÂÐ`ÄÂMýÁÆÅ( ¹ÙÍ{_-K¼ÖÅßA]w5Z»;ãT$_²ñ.6}¤æèi}Ô,Ͻ.ªÜ$òü!{ÔôFÛ¬¥y£ÉTü:öË,æpèÀ/z×í [EMAIL PROTECTED];[EMAIL PROTECTED] Pp&pNÒBBQÏ(L=òpAXP¶{¼B»Q¾ÁÂýÛp©ITè"¸À}`y½ïqv¿ GÎRX±ºcíÿBK>ײdÐ×T}é;(< eÉzö J&Q,[EMAIL PROTECTED] ³¶"òÏ976èEË=¹²ãEpÙ0òü¡' [EMAIL PROTECTED] ,#F9~Z±P e\}nüdDÉò, ³[=8 ö#ʯÑRY>aÄ÷öÙÁãwfö µþ C/sÏ,Y2WNâ·µfÑ qRWVáÏFfÁdunÂSî8&!XÙút~ð×bbª>5᧠U°¢¨©¾`júdýÇzVoÿCoý>þ·{æÚ½õ^ï>rp&§ ,[EMAIL PROTECTED]@ ¦BÃhª«nb=h á/pÑHZ^¬áõif ·?!Óë»é¸F§ 0 k¸ZÛr0§}Z¶5¨¾ì'ºX%Ëu¤4±ífÛK|ÊËÖÊÞÉñëÃ7WOÞí®>yÒÞ^ÈM·YÒV*Sßç»0CÔÂ|R2zhðÛ"NJ/TO¥4Ö#UX æì¡'K©.ë:ARqBLØ'[EMAIL PROTECTED] ÐtInPe[FjbJup9 8 ªwPǹrÇ9 õ§:¨4)Ûå¡ÑeøÏW¾®c¦Ú°« ½°Zøn]/s¯~¬0sÉÙúrýòÚçzðÅúö9 ê&?«=fB5×/ï÷ÉÛÍÚteÿ¸ÜbÚ® <1ìÄ ÓrÀú:[EMAIL PROTECTED]:j¸ÑÎåî~¹<ëåËÎr)SøRÔMW¨m5ÈóuÂÐÊÖ<¥vZös°£f´çT)}vÆgé2R)t±LaüZwªã{}£ïÊm-¹]¹¢Îg 2îÁ×CXP´\í©ÔVÜMÇ´üØ µaoÙkªÂ1qML]ª|"oPÍsØ_4úLÉÂXâ©nt³°Ñf*=çd2ã)'<*^/.k;W=èÆ.Î×]ðF}8vÿÂߧÅÑT$±[Û_ß«'Q=èÉM¼ºË NÂàPet-öÙX¼Á·oª9 J¯d#ñ2κx¦HMy·0¿g>íéM£rün £ÈìDIÛä¼±ePGEo{Ýîb¼ýKJm v¸¶nÄAÄ»×è ã¼Áï×¢¾ ôPÖRÕî[HþÌVÃÒo$K2üv²Uoñº½Ö8óWëv37«:?pË[cÅBïÁr}ÄÒ¢½º].Ìo>× yÞ- Ú<[EMAIL PROTECTED]"ÇöÈãëå¬ßç:¬Pþøå¨5×^ü¡øVZ+3·:ÆØ-Áqâ>°þ5¢ÈÐ ZvÒäÇYÂ3¡E6'òø®'aýÐvÁ'^RôJè(À ´ýüD¿'§ç°M'%èØ°ÐÊY©D³ ¡¯?¼g*lóV¿°Äz)âÙ*Ì{±/{®½*1m°¬8ÁtàרíV±¦:ÒÕ^!0 2?ÀÀ ß{ú#©ó|§ºË¢û(u²øO¹±ºÒWÅÜ~â¯Rè=i¼Ûýù¤FY>p!ÈÌ,ïUÇ/]êÏZªÒUGßõÝÐVt5däS?&:õ ·ÆÀ±P;Ìt6IúÚ±>ÑC1ÖÆSàK{jÎ/ã¶"Ñ ì½?Û?<[]´Ipbu7ÔñC>ÁØ1F.KÎ i1saNjv7oy¦Kh-Vo&RÅi s´ôª?Q ¦µ2B¸~ÌÓa± àB¼ÏÝ°Ý£â©nåÂäʱ¸ºf¶çîhá¯U«¶~ZeîX×êîme¡ Æ ÂþÁù¼=ÇU¼*P£UÖNJ]×[/±ÏµôþGq,¢H3ÅÀ§ìÅÓ7,¤Ä)[EMAIL PROTECTED]"B*.Á9'bÝ8½+vÔôì{¦GgJ ëHßÊwbZ/©æù²1KéŽÌuó.ÇH|L{Ëí*\Fݼ"¸A9:Pö]QQåòÚhEpyäÎMªY°`ùUÌæP#Wâ5°vaïì`ÿÝÓÙÁîþ»ûðøüb÷è.ÎNÞ¿::8{rrqxü¦ÒkDÆ;Fª gÿf8:çߨø©FþhÇÞP]GóÓÂ9FùÉ9ÆÅ N-PE#´Ú\qÀðyEFAMéØbà§)Z1ÛHîÈ#]¨³Ênhre¸®>C£H³ÁÊÓÕxÐD¸ÇÌâÐSe£3yá¥ûk«Õµ»/h/Ô^BÙù ý.Æ*»Ç]Ͷ¬÷Lf%I3PÀñ~0ªâ>,ÊY,Ê,ÊGÀ¢¬Ç¢¬`QÎbQÎPÎPÎPÎPÎP2(Ôö:â£CR÷áVèm!»ù µ[TÝu»>OƳõTÐc*êÀèÁªaBÁëL¯aùOÖð·×Ñtû/·_Ó;f«tþÁC§<¿hÈ´Û3гÐÖö)>ú0JÇ|9"w5 ³ûCL5S>?§P.Z([EMAIL PROTECTED] %%Øs-K¹¶:g¼j£}zð\µùâSÕªAiôU¢ÎQL^8ÅêPcHò4ñq¨%ñuâ4Úï0NñW$}8:ãxú£ßw0EU{ÙLYûl$`¦Mű¶áæe¥ÒUd©H¾MÓÜxîy£8'_LÝgÓþÁÞl´ßFÌG8qÆýnw:Ú¥óÓ]> ªªeù$M$5?ÙÊ/åÀE¤OåGÈkùZ*ãÓ×W>#ÙÅ S¼Ycî;Pkí3+di öо¯U3æµt5 ù©Ï%-s|áb»ÅMxQÌÇi3ü,ѳ{t¤¶M¶ !exêQ ~6À£Jv»qè~vfs°Q!Üêoâ£#1½¬!¥N];quô)Z) ú-Éáq*F*¯ËÝúã÷]Ãoü$ i:v>eÍNÎNCØ==ä3¸bé´À¹££&ï.5W¤ÆUOò~[M ¢ ]æ>¦n:ËGÄ1±>?9owàÛ(Iäþ³$ùè;Øu÷°§'穬J¿H'Ú÷¢¹Ô4I0'Äù±1Éf»´käòuØ®`½6æy ïpô²×9Õ0*¢¥§9\^¿Ù<fVÌê ÿ§¸¼ï+ñ£ÇnB ~°ÄÒ³aØjÇ{4ê90}òYc¦|ÐY×WÙ¢o¶kIÖ´;¥Ý548AdBY<µt<Ï'©9à;¨{$~K=ʦ¹sâúùà ^yß¾êRÑØRk*¹ÿÇôV Èe½¨Öå»Ìÿ?þÿÀEqhêJ-¯*fñû ÁUI'`e!Ã~~^ýÓÿ`úë0]Y®¬y©Õ·Uõ
[Xenomai-core] Script marking
Hi, at Debian, I noticed that the "run" scripts are not marked as such and therefore produce "lintian errors". Consider the attached patch that I propose. Besides, the documentation seems to be installed under /usr/share/doc/xenomai-2.4.2. Shouldn't /usr/share/doc/xenomai be more appropriate? (I implemented the latter in Debian.) Further, I updated the package in Debian with the suggested changes. bye, Roland diff -ruN xenomai-2.4.2/src/testsuite/clocktest/Makefile.am xenomai-2.4.2.new/src/testsuite/clocktest/Makefile.am --- xenomai-2.4.2/src/testsuite/clocktest/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/clocktest/Makefile.am 2008-02-28 21:29:24.0 +0100 @@ -14,7 +14,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: diff -ruN xenomai-2.4.2/src/testsuite/cyclic/Makefile.am xenomai-2.4.2.new/src/testsuite/cyclic/Makefile.am --- xenomai-2.4.2/src/testsuite/cyclic/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/cyclic/Makefile.am 2008-02-28 21:34:34.0 +0100 @@ -14,7 +14,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: diff -ruN xenomai-2.4.2/src/testsuite/irqbench/Makefile.am xenomai-2.4.2.new/src/testsuite/irqbench/Makefile.am --- xenomai-2.4.2/src/testsuite/irqbench/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/irqbench/Makefile.am 2008-02-28 21:31:22.0 +0100 @@ -34,7 +34,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: diff -ruN xenomai-2.4.2/src/testsuite/latency/Makefile.am xenomai-2.4.2.new/src/testsuite/latency/Makefile.am --- xenomai-2.4.2/src/testsuite/latency/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/latency/Makefile.am 2008-02-28 21:32:02.0 +0100 @@ -18,7 +18,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: diff -ruN xenomai-2.4.2/src/testsuite/switchbench/Makefile.am xenomai-2.4.2.new/src/testsuite/switchbench/Makefile.am --- xenomai-2.4.2/src/testsuite/switchbench/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/switchbench/Makefile.am 2008-02-28 21:32:38.0 +0100 @@ -17,7 +17,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" >> $(DESTDIR)$(testdir)/run @chmod +x $(DESTDIR)$(testdir)/run uninstall-local: diff -ruN xenomai-2.4.2/src/testsuite/switchtest/Makefile.am xenomai-2.4.2.new/src/testsuite/switchtest/Makefile.am --- xenomai-2.4.2/src/testsuite/switchtest/Makefile.am 2007-12-09 11:46:39.0 +0100 +++ xenomai-2.4.2.new/src/testsuite/switchtest/Makefile.am 2008-02-28 21:30:41.0 +0100 @@ -14,7 +14,8 @@ install-data-local: $(mkinstalldirs) $(DESTDIR)$(testdir) @sed -e's,@exec_prefix\@,$(exec_prefix),g' $(srcdir)/runinfo.in > $(DESTDIR)$(testdir)/.runinfo - @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$*" > $(DESTDIR)$(testdir)/run + @echo "#!/bin/sh" > $(DESTDIR)$(testdir)/run + @echo "\$${DESTDIR}$(exec_prefix)/bin/xeno-load \`dirname \$$0\` \$$
Re: [Xenomai-core] Xenomai in Debian
Gilles Chanteperdrix wrote: >> The binary package list changed to adjust to Debian conventions: >> >> xenomai-runtime >> linux-patch-xenomai >> libxenomai1 >> libxenomai-dev >> xenomai-doc > > So, I need to install all these packages, then continue at make-kpkg ? Similar to the Wiki description before. You certainly don't _need_ xenomai-doc for make-kpkg. Some of the other packages can be missing, will need to check later. But I'm sure you already know it better: xenomai-runtime is all the executables (except xeno-config), libxenomai-dev is the installed header files, xeno-config and static libs, libxenomai1 is the shared lib. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Xenomai in Debian
Hi Gilles, Gilles Chanteperdrix wrote: > The current help on Xenomai Debian packages is: > http://www.xenomai.org/index.php/Building_Debian_packages > > Is this documentation still valid when using pre-built packages ? Thanks for the note! The binary package list changed to adjust to Debian conventions: xenomai-runtime linux-patch-xenomai libxenomai1 libxenomai-dev xenomai-doc bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package
Jan Kiszka wrote: > Ah, I see... that powerpc already failed. :-> Of course... The DEBIAN/control "hackery" is operating on an architecture independent package (linux-patch-xenomai), while only building the architecture dependent packages on the build daemons... Will be fixed in next revision... Thanks for the note! Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package
Leopold Palomo-Avellaneda wrote: > Also, xenomai could run in a IA64 .. Anyone tested it? I can just declare it in the Debian package. If it's untested, maybe I need to dedicate one of the IA64 machines here to Xenomai... :-) Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Debian package
Hi, I hope you don't mind that we move this to the xenomai-core mailing list with CC, since I fear the same questions will be raised again there at some point. Jan Kiszka wrote: > Now the next question: You are providing i386 packages so far. Do you > have plans for x86-64 as well? The respective debian/control line currently is: Architecture: amd64 arm i386 ia64 powerpc At http://packages.qa.debian.org/x/xenomai.html , you can also see the current status of the different architectures' build daemons (i.e., a link to the logs). bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] Xenomai in Debian
Hi, thanks to the previous Debian packaging work of Paul Corner (and of course, all the Xenomai core developers), we now have xenomai officially in Debian (i.e. Debian "sid", ready for the next Debian release "lenny"). For Debian related bugs, please use the Bug Tracking System at bugs.debian.org. Everything else should stay the same as before, except that all the Debian related files under debian/ are maintained inside Debian (and can be backported to Xenomai "upstream", if desired in Xenomai SVN). Have fun, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core