From: Wolfgang Grandegger <wg@domain.hid>
To: Peter Soetens <peter.soetens@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] v2.2.6 prepare-kernel.sh broken for 2.4 kernels
Date: Tue, 03 Apr 2007 12:50:30 +0200 [thread overview]
Message-ID: <46123176.1080503@domain.hid> (raw)
In-Reply-To: <200704031134.33726.peter.soetens@domain.hid>
Peter Soetens wrote:
> Hi,
>
> It seems some files are missing in this (not announced ?) release, which make
> the prepare-kernel.sh script fail in the following fcn:
>
> patch_help() {
> if which perl > /dev/null; then
> hfile=$linux_tree/Documentation/Configure.help
> if ! grep -iq CONFIG_XENO $hfile; then
> kfiles=$xenomai_root/scripts/Kconfig.frag
> for d in ksrc/nucleus ksrc/skins ksrc/arch/$xenomai_arch \
> ksrc/drivers sim; do
>
> -> 'sim' is not found
>
> kfiles="$kfiles `find $xenomai_root/$d -name Kconfig`"
> done
> perl $xenomai_root/scripts/help_from_kconfig.pl $kfiles >> $hfile
>
> -> help_from_kconfig.pl is not found.
>
> if test x$verbose = x1; then
> echo 'Configuration help added.'
> fi
> fi
> fi
> }
>
> It seems (afaikt) to be related to this patch:
> <https://mail.gna.org/public/xenomai-core/2006-11/msg00037.html>
>
> Which did not patch the Makefile.am file to include the script in the
> EXTRA_DIST var. The 'sim' dir seems to be a Xenomai 2.0.x slip-in.
A similar problem has been reported in December 2006 with another
release. Search for the subject "prepare kernel fails". Some files are
missing or not up-to-date in this release :-(.
Wolfgang.
next prev parent reply other threads:[~2007-04-03 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 9:34 [Xenomai-help] v2.2.6 prepare-kernel.sh broken for 2.4 kernels Peter Soetens
2007-04-03 10:50 ` Wolfgang Grandegger [this message]
2007-04-03 14:18 ` Philippe Gerum
2007-04-03 15:19 ` Philippe Gerum
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=46123176.1080503@domain.hid \
--to=wg@domain.hid \
--cc=peter.soetens@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.