All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] consolidate testsuite installation
Date: Sun, 10 Dec 2006 20:22:29 +0100	[thread overview]
Message-ID: <1165778549.8255.17.camel@domain.hid> (raw)
In-Reply-To: <457BDF99.1020405@domain.hid>

On Sun, 2006-12-10 at 11:21 +0100, Jan Kiszka wrote:
> The only part of the Xenomai user-space package not yet following
> standard installation rules is the testsuite. It gets installed to
> $prefix/testsuite, by default /usr/testsuite. The attached patch is an
> approach to overcome this unusual layout.

Ack. Implementation-wise, we have to fix the following though:

xeno-load.in needs to be fixed, so that passing a single dot as argument
correctly picks the default runinfo target in the current directory.
This currently does not work as expected.

The second patch works around a problem with sudo relying on the
contents of the user's PATH variable. This won't work for people using a
version of sudo compiled with the secure path option by their favourite
distro. In that case, /usr/xenomai/bin (or whatever the user picked to
install xenomai) won't appear in that secure path, so the binary program
given in the runinfo file won't be found. A possible option is to
provide a relative path to locate the binary program,
e.g. ../../../../bin/latency for the latency test, as the example patch
shows. Not pretty, but the other way would need to autoconfiscate the
runinfo files, or at least run them through sed before installing, so
that we could substitute some placeholder with $exec_prefix.

--- scripts/xeno-load.in	(revision 1936)
+++ scripts/xeno-load.in	(working copy)
@@ -37,7 +37,7 @@
      target_dir=`pwd`
   fi
   if test "x$target_name" = x; then
-     if `echo $target_dir | grep -q /`; then
+     if `echo $target_dir | grep -q -e / -e .`; then
         target_name=default
      else
         target_name=$target_dir
Index: src/testsuite/latency/runinfo
===================================================================
--- src/testsuite/latency/runinfo	(revision 1936)
+++ src/testsuite/latency/runinfo	(working copy)
@@ -1 +1 @@
-latency:native+rtdm+timerbench:!latency;popall:control_c
+latency:native+rtdm+timerbench:!../../../../bin/latency;popall:control_c

-- 
Philippe.




  reply	other threads:[~2006-12-10 19:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10 10:21 [Xenomai-core] [PATCH] consolidate testsuite installation Jan Kiszka
2006-12-10 19:22 ` Philippe Gerum [this message]
2006-12-11  0:16   ` Jan Kiszka
2006-12-11  9:07     ` Philippe Gerum
2006-12-11  9:24       ` Jan Kiszka
2006-12-11 10:14         ` Philippe Gerum
2006-12-12  8:36         ` Gilles Chanteperdrix
2006-12-12 12:32           ` Jan Kiszka
2006-12-12 13:12             ` Gilles Chanteperdrix
2006-12-12 13:24               ` Jan Kiszka
2006-12-12 14:46                 ` Gilles Chanteperdrix
2006-12-13 16:58                   ` Jan Kiszka
2006-12-18  9:42                     ` Gilles Chanteperdrix
2006-12-18 12:30                       ` Jan Kiszka
2006-12-18 13:32                         ` Gilles Chanteperdrix
2006-12-18 14:27                           ` Jan Kiszka

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=1165778549.8255.17.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@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.