From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: 4Front Technologies <dev@opensound.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to check if kernel sources are installed on a system?
Date: Thu, 25 May 2006 18:12:45 -0600 [thread overview]
Message-ID: <20060525181245.A3859@openss7.org> (raw)
In-Reply-To: <44763AE0.6050907@opensound.com>; from dev@opensound.com on Thu, May 25, 2006 at 04:16:48PM -0700
Dev,
It appears that you might be fairly new to the game of maintaining open
source kernel modules outside of mainline. Having worked for a number
of years providing STREAMS distributions outside of mainline and that
need to be compatible with a wide range of distributions, I spent some
amount of time developing a GNU autoconf/automake based approach that
works with most major distributions.
Even though Linux Fast-STREAMS has proven that STREAMS-based pipes can
outperform Linux SVR 3.2 based pipes under FC4 (see
http://www.openss7.org/streams_perf.html ), and current UDP tests show
that STREAMS easily rivals a sockets-based approach, strong dogmatic
opinions against STREAMS keeps it from being accepted in the mainline
(see http://www.tux.org/#s9-9 ).
You seem to be in a similar circumstance. What the autoconf macros
developed as part of the OpenSS7 Project do are as follows:
- identifies the distribution
- identifies the running or target kernel
- locates configured sources appropriate for build
- identifies other LSB related issues such as init scripts
- builds source and binary RPM packages and source and binary Debian
packages
Several common issues with building outside the kernel tree on
production distributions addressed are as follows:
- provides access to non-exported symbols (note that OpenSS7 is released
under GPLv2 so there are no issues for OpenSS7 packages).
- provides methods for performing all autoconf tests against kernel
headers or source. Often for production distributions testing kernel
version is not sufficient because kernels have been hacked by the
distributor: this provides a means to test the actual kernel rather
than basing tests on kernel versions.
- extracts compilation flags from kernel Makefiles and works with both
2.4 and 2.6 kernel series, as well as distribution-hacked makefiles.
- by identifying the distribution, locates kernel sources and
configuration files in a distribution dependent fashion.
- suitable for use with RPM spec files and Debian build scripts.
If you would like to take a look, download the streams-0.7a.4.tar.bz2
from http://www.openss7.org/download.html and take a look at the
autoconf macros in the m4 subdirectory, the automake makefile fragments
in the am subdirectory, scripts in the scripts subdirectory,
acinclude.m4, the streams.spec.in RPM spec file, and the debian
subdirectory.
If there is sufficient interest, I would entertain separately
maintaining the autoconf/automake fragments.
--brian
On Thu, 25 May 2006, 4Front Technologies wrote:
> Jesper Juhl wrote:
> > On 26/05/06, 4Front Technologies <dev@opensound.com> wrote:
> >>
> >> Anything to get out-of-kernel modules compiling without jumping
> >> through 1000
> >> hoops is good.
> >>
> >
> > hmm, I'd say that anything that encourages people to merge their code
> > with mainline instead of maintaining out-of-tree modules is good.
> >
>
>
> Honestly, if I put Open Sound drivers under GPL would Linus really merge my code
> back into the kernel?. Be honest!
>
>
> If you aren't going to maintain OSS, then give me a way to support my product!.
>
>
>
>
>
> best regards
>
> Dev Mazumdar
> -----------------------------------------------------------
> 4Front Technologies
> 4035 Lafayette Place, Unit F, Culver City, CA 90232, USA.
> Tel: (310) 202 8530 URL: www.opensound.com
> Fax: (310) 202 0496 Email: info@opensound.com
> -----------------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Brian F. G. Bidulock ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org ¦ world; the unreasonable one persists in ¦
http://www.openss7.org/ ¦ trying to adapt the world to himself. ¦
¦ Therefore all progress depends on the ¦
¦ unreasonable man. -- George Bernard Shaw ¦
next prev parent reply other threads:[~2006-05-26 0:12 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 21:19 How to check if kernel sources are installed on a system? devmazumdar
2006-05-25 21:27 ` alan
2006-05-25 21:29 ` Jan-Benedict Glaw
2006-05-25 22:02 ` Lee Revell
2006-05-25 22:15 ` 4Front Technologies
2006-05-25 22:25 ` Lee Revell
2006-05-25 22:34 ` Dave Jones
2006-05-25 22:40 ` Lee Revell
2006-05-25 21:29 ` Valdis.Kletnieks
2006-05-25 21:35 ` Dave Jones
2006-05-25 21:32 ` Michal Piotrowski
2006-05-25 21:34 ` Jeff Garzik
2006-05-25 21:39 ` Jan-Benedict Glaw
2006-05-25 21:42 ` Jeff Garzik
2006-05-26 14:36 ` Jan-Benedict Glaw
2006-05-25 21:44 ` Dave Jones
2006-05-25 22:52 ` Olivier Galibert
2006-05-26 4:23 ` Willy Tarreau
2006-05-26 14:37 ` Jan-Benedict Glaw
2006-05-26 15:01 ` linux-os (Dick Johnson)
2006-05-27 10:47 ` Jesper Juhl
2006-05-25 21:41 ` Dave Jones
2006-05-25 22:29 ` Lee Revell
2006-05-25 22:39 ` 4Front Technologies
2006-05-25 23:06 ` Jesper Juhl
2006-05-25 23:16 ` 4Front Technologies
2006-05-26 0:12 ` Brian F. G. Bidulock [this message]
2006-05-25 23:00 ` Diego Calleja
2006-05-26 0:24 ` Måns Rullgård
2006-05-26 14:29 ` Arjan van de Ven
2006-05-26 15:35 ` Brian F. G. Bidulock
2006-05-27 12:21 ` Arjan van de Ven
2006-05-27 19:52 ` Brian F. G. Bidulock
2006-05-27 20:21 ` Arjan van de Ven
2006-05-27 22:21 ` Brian F. G. Bidulock
2006-05-28 8:27 ` Arjan van de Ven
2006-05-28 10:13 ` Brian F. G. Bidulock
2006-05-27 14:41 ` Kyle Moffett
2006-05-27 22:05 ` Brian F. G. Bidulock
2006-05-28 13:03 ` Heiko Carstens
2006-05-28 13:12 ` Jan-Benedict Glaw
2006-05-28 13:45 ` Heiko Carstens
2006-05-28 17:03 ` Arjan van de Ven
2006-05-28 17:52 ` Lee Revell
2006-05-28 18:12 ` Arjan van de Ven
2006-05-28 18:22 ` Randy.Dunlap
2006-05-28 19:10 ` Willy Tarreau
2006-05-28 19:55 ` Lee Revell
2006-05-28 20:45 ` Jan-Benedict Glaw
2006-05-28 21:27 ` Lee Revell
2006-05-28 21:55 ` Jan-Benedict Glaw
2006-05-28 22:02 ` Lee Revell
2006-05-28 22:38 ` Jan-Benedict Glaw
2006-05-29 12:11 ` Steven Rostedt
2006-05-29 12:38 ` Steven Rostedt
2006-05-29 4:44 ` Brian F. G. Bidulock
2006-05-29 4:52 ` Arjan van de Ven
2006-05-29 5:35 ` 4Front Technologies
2006-05-29 5:46 ` David Miller
2006-05-29 5:59 ` Valdis.Kletnieks
2006-05-29 6:09 ` Willy Tarreau
2006-05-29 6:11 ` Arjan van de Ven
2006-05-29 6:57 ` Brian F. G. Bidulock
2006-05-29 7:01 ` Arjan van de Ven
2006-05-29 7:29 ` Brian F. G. Bidulock
2006-05-29 7:05 ` 4Front Technologies
2006-05-29 7:23 ` Brian F. G. Bidulock
2006-05-29 7:43 ` Valdis.Kletnieks
2006-05-29 12:23 ` Arjan van de Ven
2006-05-29 15:52 ` Christopher Friesen
2006-05-29 16:00 ` Arjan van de Ven
2006-05-28 20:40 ` Jesper Juhl
2006-05-25 22:51 ` Jesper Juhl
2006-05-26 0:09 ` Thomas Backlund
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=20060525181245.A3859@openss7.org \
--to=bidulock@openss7.org \
--cc=dev@opensound.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox