From: Jan Kiszka <jan.kiszka@domain.hid>
To: niklaus.giger@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: AW: [Xenomai-help] prepare kernel fails
Date: Wed, 20 Dec 2006 18:42:27 +0100 [thread overview]
Message-ID: <45897603.5070703@domain.hid> (raw)
In-Reply-To: <200612201831.12472.niklaus.giger@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]
Niklaus Giger wrote:
> Am Mittwoch, 20. Dezember 2006 09:48 schrieb Gilles Chanteperdrix:
>> Niklaus Giger wrote:
>>> Am Dienstag, 19. Dezember 2006 21:38 schrieb Jan Kiszka:
>>>> I rather think c) is desired: checkout from svn, make dist, untar that
>>>> archive and continue to work with *those* sources.
>>> This solution is also easily integretable into the actual Buildbot. I
>>> suppose do it would be sufficient to add it only to the daily "full"
>>> builds. But I would need to know how the release is exactly generated.
>>> E.g. after a checkout to clean directory there is no Makefile and
>>> therefore "make dist" fails miserably. Could somebody please tell me the
>>> exact steps?
>> You need to create a build tree by running the configure script, then
>> run make dist (or preferably "make distcheck") in this build tree.
> What are the needed (minimal) options for configure? Because if I do not
> specify any option I get the following error when running make:
>> make[2]: Entering directory `/home/hcu/kernel/tst_dist/src/testsuite'
>> list='latency switchbench cyclic switchtest irqbench'; for subdir in $list;
>> do \ if test "$subdir" = .; then :; else \
>> test -dbuild
>> "/home/hcu/kernel/tst_dist/xenomai-2.2.92/src/testsuite/$subdir" \
>>
>> || mkdir -p --
>> || "/home/hcu/kernel/tst_dist/xenomai-2.2.92/src/testsuite/$sub
>> ||dir" \ exit 1; \
>>
>> distdir=`CDPATH="${ZSH_VERSION+.}:" && cd
>> /home/hcu/kernel/tst_dist/xenomai-2.2.92/src/testsuite && pwd`; \
>> top_distdir=`CDPATH="${ZSH_VERSION+.}:" && cd
>> /home/hcu/kernel/tst_dist/xenomai-2.2.92 && pwd`; \ (cd $subdir && \
>> make \
>> top_distdir="$top_distdir" \
>> distdir="$distdir/$subdir" \
>> distdir) \
>>
>> || exit 1; \
>>
>> fi; \
>> done
>> make[3]: Entering directory
>> `/home/hcu/kernel/tst_dist/src/testsuite/latency' make[3]: *** No rule to
>> make target `runinfo', needed by `distdir'. Stop. make[3]: Leaving
>> directory `/home/hcu/kernel/tst_dist/src/testsuite/latency' make[2]: ***
>> [distdir] Error 1
>> make[2]: Leaving directory `/home/hcu/kernel/tst_dist/src/testsuite'
>> make[1]: *** [distdir] Error 1
>> make[1]: Leaving directory `/home/hcu/kernel/tst_dist/src'
>> make: *** [distdir] Error 1
>
> Do I need to run this on a system which is running a xenomai kernel?
> (I never tried to run it on my Intel MacMini.) Can I build it on a PPC
> machine?
Argh, fallout from my last changes.
I fixed the Makefile.ams in SVN, but someone with fitting automake
(Gilles?) has to run bootstrap. I'm getting now even more diffs with my
toolchain than yesterday.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-12-20 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 14:00 AW: [Xenomai-help] prepare kernel fails Roderik_Wildenburg
2006-12-18 14:08 ` Jan Kiszka
2006-12-18 14:39 ` Gilles Chanteperdrix
2006-12-18 20:25 ` Philippe Gerum
2006-12-19 8:51 ` Gilles Chanteperdrix
2006-12-19 21:38 ` Philippe Gerum
2006-12-19 19:54 ` Niklaus Giger
2006-12-19 20:38 ` Jan Kiszka
2006-12-19 21:02 ` Niklaus Giger
2006-12-20 8:48 ` Gilles Chanteperdrix
2006-12-20 17:31 ` Niklaus Giger
2006-12-20 17:42 ` Jan Kiszka [this message]
2006-12-20 17:48 ` Gilles Chanteperdrix
2006-12-20 20:09 ` Niklaus Giger
2006-12-20 20:19 ` Niklaus Giger
2006-12-21 8:52 ` Gilles Chanteperdrix
2006-12-21 9:05 ` Jan Kiszka
2006-12-18 14:25 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2006-12-18 13:41 Roderik_Wildenburg
2006-12-18 14:02 ` Wolfgang Grandegger
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=45897603.5070703@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=niklaus.giger@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.