Philippe Gerum wrote: > On Mon, 2007-07-09 at 17:14 +0200, Jan Kiszka wrote: >> Wolfgang Grandegger wrote: >>> Jan Kiszka wrote: >>>> Philippe Gerum wrote: >>>>> On Mon, 2007-07-09 at 16:45 +0200, Wolfgang Grandegger wrote: >>>>>> Hello, >>>>>> >>>>>> the attached patch changes: >>>>>> >>>>>> 2007-07-09 Wolfgang Grandegger <[EMAIL PROTECTED]> >>>>>> >>>>>> * include/asm-generic/wrappers.h: add __deprecated for Linux 2.4. >>>>>> >>>>> Merged, thanks. >>>> You are too fast for me - I was still test-building my approach! >>> Too fast? My i-Pipe patched Linux 2.4 kernel did simply not built ;-). >> Yeah, and my 2.4 kernel was lying around in the corner, slightly dusty, >> definitely not touched for several months. >> >> Hell, the amount of regressions one (specifically I) can produce due to >> all this config variants is amazing. > > We all have a very well defined job in this project, and particularly: > - I do produce the original silly bugs. > - You are in charge of adding regressions to your past fixes of my bugs > - Dmitry is in charge of finding why our common code breaks. > - Wolfgang is in charge of making all the involved fixes compile > properly. > - Gilles is in charge of making the result run on bugous and/or sluggish > hardware. > > Ok, all in all, my situation is the best one. Good.
Yeah, it's certainly not bad when the boss is happy. :) > >> What would be really nice is a >> playground for patches, some build system you could post a patch series >> and a set of .configs to and that will then "simply" try to generate >> various kernels and the xenomai userland for various archs >> automatically, reporting back any errors or warnings. Without going >> through SVN with the changes every time. Just a dream. > > Niklaus already built most of this infrastructure for us, only the > automated patching part seems to be missing so far: > http://ngiger.dyndns.org/buildbot/ I'm very well aware of his work, but I also know that it was never intended for broad use due to hardware and bandwidth constraints. However, his buildbot scripts may indeed provide a helpful foundation. > We would also have to alleviate the burden of his server by providing > some dedicated hardware to do that, though. That together with the required software infrastructure for more automation are the points. We need some nice parallel box (4-way or more) with a fast link and someone to look after the software. The latter work may partly be distributed among the arch maintainers (toolchain, kernel, .config updates). One could go even further with such a platform, e.g. qemu targets, but let's concentrate on multi-arch, multi-kernel build services first. (My worries are also a bit egoistic: the nice 4-way box I'm using so far for certain builds and tests will be definitely out of reach for me in the near future.) Jan
Description: OpenPGP digital signature
_______________________________________________ Xenomai-core mailing list Xenomaifirstname.lastname@example.org https://mail.gna.org/listinfo/xenomai-core