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@xenomai.org
Subject: Re: [Xenomai-core] Problems building RTnet
Date: Wed, 23 Aug 2006 22:49:34 +0200	[thread overview]
Message-ID: <1156366174.4401.77.camel@domain.hid> (raw)
In-Reply-To: <44ECB7EF.7050300@domain.hid>

On Wed, 2006-08-23 at 22:17 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Niklaus Giger wrote:
> >> Hi 
> >>
> >> Since a few hours RTnet cannot even be configured, as the Xenomai version got
> >> bumped to 2.3-devel. See
> >> http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0
> >> Where it says:
> >>
> >> checking for Xenomai version... configure: error: *** Unsupported Xenomai 
> >> version 2.3-devel in /var/buildbot/slave/tqm860/linux
> > 
> > Fixed (for the next versions now as well...).
> > 
> >> This morning the buildbot complained like the following:
> >> powerpc-860-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../config   -g -I. -I/usr/xenomai/include -g -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -I../../../stack/include -I../../../stack/include -g -MT 
> >> rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_ifs.c; 
> >> \
> >>         then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else 
> >> rm -f ".deps/rtnet_ifs.Tpo"; exit 1; fi
> >> In file included from rtnet_ifs.c:31:
> >> ../../../stack/include/rtnet.h:29:23: rtdm/rtdm.h: No such file or directory
> > 
> > There must be still something wrong with the xenomai user-space
> > installation. Check if the xeno-config handed to RTnet returns
> > reasonable paths and if those paths contain the files we need here.
> > 
> 
> Looks like a DESTDIR-or-not-DESTDIR question in the include (and lib?)
> paths xeno-config returns. Do we need two runs for the Xenomai lib
> installation, one for the target and one for the build host? Or is RTnet
> supposed to add DESTDIR to all paths returned by xeno-config? Tricky,
> too tricky for tonight.

$ DESTDIR=/foo xeno-config ...
would make xeno-config prepend the staging directory to the output paths
when appropriate.

> 
> Jan
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
-- 
Philippe.




      reply	other threads:[~2006-08-23 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 18:58 [Xenomai-core] Problems building RTnet Niklaus Giger
2006-08-23 19:59 ` Jan Kiszka
2006-08-23 20:17   ` Jan Kiszka
2006-08-23 20:49     ` Philippe Gerum [this message]

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=1156366174.4401.77.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.