From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] xenomai release check
Date: Fri, 13 Jul 2007 10:06:40 +0200 [thread overview]
Message-ID: <1184314000.6014.213.camel@domain.hid> (raw)
In-Reply-To: <4696A9BE.4090008@domain.hid>
On Fri, 2007-07-13 at 00:22 +0200, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Thu, 2007-07-12 at 10:53 +0000, Stéphane ANCELOT wrote:
> >> Hi,
> >>
> >> Is it possible to setup a function that returns the xeno version string ?
> >>
> >
> > Have a look at XENO_VERSION_CODE and friends in nucleus/version.h
>
> I think Stephan has a different problem:
>
> >
> >> In cross compiled environment, this will permit to check at runtime that
> >> you are running the program with the expected xeno libraries !!!
> >>
> >> We have had following problem on the target we setted up:
> >> kernel modules were right, but usr/xenomai/libs were coming from an
> >> older xeno release !!
> >> at runtime , our program had some bad issues !
>
> He dynamically linked against some old Xenomai lib over a new kernel,
> right? That should be caught by the ABI check on library init these
> days. Stephan, can you tell us which versions where involved here?
>
Not if the ABI numbers haven't changed, so the real question is: which
discrepancy did actually caused the issue, and does it reveal a lack in
updating the ABI revs, or a plain application issue.
> Jan
>
--
Philippe.
next prev parent reply other threads:[~2007-07-13 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 10:53 [Xenomai-help] xenomai release check Stéphane ANCELOT
2007-07-12 17:38 ` Philippe Gerum
2007-07-12 22:22 ` Jan Kiszka
2007-07-13 8:06 ` Philippe Gerum [this message]
2007-07-13 10:54 ` Stéphane ANCELOT
2007-07-13 12:35 ` 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=1184314000.6014.213.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.