All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jeff Webb <jeff.webb@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Compiling Linux+Xenomai 32bits kernel on	FC6	x86_64?
Date: Wed, 17 Jan 2007 21:00:34 +0100	[thread overview]
Message-ID: <45AE8062.7050701@domain.hid> (raw)
In-Reply-To: <45AE7D81.9050007@domain.hid>

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

Jeff Webb wrote:
> Jan Kiszka wrote:
>> Hmm, that tickles my fantasy once again: Could we derive generic .specs
>> from your files to include them in the Xenomai distribution? Then some
>> additional Makefile rules could provide a "make rpm" that generates
>> packages for kernel and userland (when given some kernel.tar.bz2).
>> Basically, your steps generalised and automated.
> 
> That would be great.  I started with the 'mkspec' script from the
> vanilla kernel tree, and added a few things that make the resulting RPMs
> work better with Fedora.  I'm not sure how other distributions handle
> things like creating an initrd, etc.  Maybe someone could post a
> kernel.spec file for the latest version of SuSE.  I can look at it and
> see how it differs from what I'm doing on Fedora.

You don't want to see it. In case so insist:

http://www.rts.uni-hannover.de/rtaddon/rpms/src/unpacked/kernel-xeno-default.spec

> 
> Right now, my spec file also creates a HUGE kernel-source RPM that
> contains the whole compiled source tree.  I really need to understand
> how the Fedora spec file creates kernel-devel RPMs that have just the
> stuff needed for compiling kernel modules.  This would be a lot better
> than having the huge kernel-source RPM that I generate now.

No clue either here (given the SuSE file...).

> 
>> This would help us to provide, e.g., an i386 pre-built package with
>> reasonable default config, something I still consider useful. But, of
>> course, it must not cost any effort :). Automated rpm generation would
>> be a big step in that direction.
> 
> I think that would be very useful to many folks.
> 
>> BTW, have you seen my Xenomai.spec for the SuSE packages I once posted?
>> Attached is an updated version. It splits the Xenomai userland in
>> several sub-packages to allow selective installation.
> 
> No, I hadn't looked at it.  That is probably a better approach.  I can
> test this on Fedora when I get a chance.

You're welcome. The userspace part should be simpler to make generic.

Jan


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

  reply	other threads:[~2007-01-17 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  8:51 [Xenomai-help] Compiling Linux+Xenomai 32bits kernel on FC6 x86_64? Eric Noulard
2007-01-17  9:06 ` Matthias Fechner
2007-01-17 15:20   ` Jeff Webb
2007-01-17 18:19     ` Jan Kiszka
2007-01-17 19:48       ` Jeff Webb
2007-01-17 20:00         ` Jan Kiszka [this message]
2007-01-18 11:18       ` Paul
2007-01-18 11:46         ` Jan Kiszka
2007-01-18 11:53           ` Jan Kiszka
2007-01-18 12:12             ` Philippe Gerum
2007-01-18 20:36             ` Paul

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=45AE8062.7050701@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=jeff.webb@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.