From: Jakub Nowacki <j.s.nowacki@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] unresolved symbol - check the xenomai installation
Date: Thu, 05 Jan 2012 23:07:31 +0000 [thread overview]
Message-ID: <4F062D33.3060606@domain.hid> (raw)
In-Reply-To: <4F049054.4000302@domain.hid>
On 04/01/12 17:45, Gilles Chanteperdrix wrote:
>
> This looks bad. Please re-run latency with no argument. If should
> normally produce a report about min/average/max latency every second. If
> it does not, I would recommend restarting the installation from scratch:
> - first uninstalling any installed version, running "make uninstall" in
> the build directory, this for xenomai 2.4.4 and 2.6.0.
> - re-run prepare-kernel, recompile the kernel, leaving the xenomai
> configuration options to their default value.
>
I have a similar problem trying to install xenomai 2.6.0. In my case
latency works correctly, but trying to compile examples gives me the
same 'unresolved reference' error. I noticed this first trying to
compile RTXI, which also gives me
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_current'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_sem_heap'
/usr/xenomai/lib/libnative.so: undefined reference to
`xeno_sigshadow_install_once'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_set_current'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_map_heap'
/usr/xenomai/lib/libnative.so: undefined reference to `xnarch_tsc_to_ns'
/usr/xenomai/lib/libnative.so: undefined reference to
`xeno_handle_mlock_alert'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_fault_stack'
/usr/xenomai/lib/libnative.so: undefined reference to
`xeno_set_current_mode'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_bind_skin_opt'
/usr/xenomai/lib/libnative.so: undefined reference to `xeno_current_mode'
/usr/xenomai/lib/libnative.so: undefined reference to `xnarch_ns_to_tsc'
I did it before with Xenomai 2.5.6 and did not recall such a linking
problems. I read before that it might be causes by cross-compilation
being messed up, but in that case I do default compilation on linux
2.6.38.8. I did not try 2.5.6 again to check if the problem remains for
2.5.6, I can try to do that.
Best wishes,
Jakub
next prev parent reply other threads:[~2012-01-05 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 14:31 [Xenomai-help] unresolved symbol - check the xenomai installation Gregory Gosse
2012-01-04 14:55 ` Gilles Chanteperdrix
2012-01-04 16:22 ` Gregory Gosse
2012-01-04 17:45 ` Gilles Chanteperdrix
2012-01-05 23:07 ` Jakub Nowacki [this message]
2012-01-06 9:40 ` Gilles Chanteperdrix
2012-01-08 20:38 ` Jakub Nowacki
2012-01-08 22:09 ` Philippe Gerum
2012-01-08 22:35 ` Jakub Nowacki
2012-01-09 12:11 ` Gilles Chanteperdrix
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=4F062D33.3060606@domain.hid \
--to=j.s.nowacki@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.