From: Philippe Gerum <rpm@xenomai.org>
To: "Ashri, Sarit" <Sashri@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Problem building MVM: "error: The X11 library '-lX11' could not be found"
Date: Sun, 04 Dec 2005 19:16:40 +0100 [thread overview]
Message-ID: <43933288.8000906@domain.hid> (raw)
In-Reply-To: <8DF1258D5F0FC94EBF5810BF2C7BF2FB400251@domain.hid>
Ashri, Sarit wrote:
> Hi Philippe,
> Do you think I should wait for the v2.1 to be released
> or is it stable enough To start playing with it now?
>
If we are still talking about the simulator, this is a rather mature
piece of code since 2000 or so. Actually, it has been adapted from an
old RTOS simulator project I recently moved to GNA:
www.gna.org/projects/carbonkernel.
> Thanks a lot for all your help!
> Sarit.
>
>
>>-----Original Message-----
>>From: Philippe Gerum [mailto:rpm@xenomai.org]
>>Sent: Thursday, December 01, 2005 2:52 PM
>>To: Ashri, Sarit
>>Cc: xenomai@xenomai.org
>>Subject: Re: [Xenomai-help] Problem building MVM: "error: The
>>X11 library '-lX11' could not be found"
>>
>>Ashri, Sarit wrote:
>>
>>>>Ashri, Sarit wrote:
>>>>
>>>>
>>>>>Hi Philippe,
>>>>>
>>>>>I did read the files. What I don't understand is how to build the
>>>>>Xenomai With Simulator support?
>>>>>When I build Xenomai without simulator support - everything
>>>>
>>>>works just
>>>>
>>>>
>>>>>fine (crossed compiled to work on PPC with Linux 2.6.13.4).
>>>>>As soon as I mark Simulator->Minute Virtual Machine I get
>>
>>that error
>>
>>>>>(X11 library..).
>>>>>I understood from reading previous mails on the internet
>>>>
>>>>that I should
>>>>
>>>>
>>>>>be able to build the MVM on my host computer which is NOT
>>>>
>>>>patched by
>>>>
>>>>
>>>>>Adeos (RHEL3.0 Linux on i686) through Regular Xenomai
>>>>
>>>>CROSS_COMPILING
>>>>
>>>>
>>>>>and installation.
>>>>
>>>>Try this:
>>>>
>>>>- Build your target system first without the simulator using
>>>>cross-compilation for ppc. Let's say that you installed the results
>>>>under /usr/realtime, which is the default.
>>>>
>>>>- Then, build the simulator separately for the host:
>>>>
>>>>$ mkdir sim-build && cd sim-build
>>>>$ .../xenomai/sim/configure --with-xeno-dir=/usr/realtime
>>>>--with-gcc-tarball=/something/gcc-2.95.3.tar.bz2
>>>>$ make install
>>>>
>>>
>>>Everything compiled fine, but when I tried to compile the
>>
>>native demo
>>
>>>for the Simulator I received the following error:
>>>cd .../skins/native/demos
>>>[demos]$ /usr/realtime/bin/gcic -o satch_s.o -c satch.c -g -I
>>>/opt/nfs_root/usr/realtime/include
>>>In file included from
>>>/opt/nfs_root/usr/realtime/include/nucleus/asm/atomic.h:23,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/system.h:33,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/asm-generic/system.h:560,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/asm/system.h:23,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/types.h:40,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/queue.h:23,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/timer.h:23,
>>> from
>>>/opt/nfs_root/usr/realtime/include/nucleus/thread.h:23,
>>> from
>>>/opt/nfs_root/usr/realtime/include/native/task.h:26,
>>> from satch.c:4:
>>>/usr/include/asm/atomic.h:40: warning: #warning Using
>>
>>kernel header in
>>
>>>userland program. BAD!
>>>In file included from
>>>/opt/nfs_root/usr/realtime/include/nucleus/system.h:33,
>>> from
>>
>>Gah. Ok, my mistake. Since you are cross-compiling for your
>>target, you need to have two Xenomai installations, once for
>>the ppc target to run the real stuff, another one to run the
>>virtual simulation environment for the x86 host.
>>
>>So, ...
>>
>>- Configure and cross-compile Xenomai for ppc without
>>simulation support for installing to /opt/nfsroot
>>- Configure and compile Xenomai natively for x86 with
>>simulation support for installing to, e.g. /opt/local
>>
>>This way at least, you won't need to build the simulator
>>apart, it will be built as part of the second step. Most of
>>the native x86 support won't be used (aside of the simulator,
>>of course), but at least, this will work. On the host, you
>>will need to set your PATH and LD_LIBRARY_PATH to
>>/opt/local/bin, and /opt/local/lib respectively, so that the
>>simulation libs and tools are found.
>>
>>The #warning won't go away though; only v2.1 gets rid of this
>>by avoiding any kernel header inclusion in user-space. Debian
>>systems would not bother you with this (at least sarge
>>doesn't), but RH actually do.
>>
>>--
>>
>>Philippe.
>>
>
> ***********************************************************************************
> This email message and any attachments thereto are intended only for use by the addressee(s) named above, and may contain legally privileged and/or confidential information. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the postmaster@domain.hid and destroy the original message.
> ***********************************************************************************
>
--
Philippe.
next prev parent reply other threads:[~2005-12-04 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 12:45 [Xenomai-help] Problem building MVM: "error: The X11 library '-lX11' could not be found" Ashri, Sarit
2005-12-04 18:16 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 12:34 Ashri, Sarit
2005-12-01 12:51 ` Philippe Gerum
2005-12-01 11:14 Ashri, Sarit
2005-12-01 11:22 ` Philippe Gerum
2005-12-01 12:24 ` Gilles Chanteperdrix
2005-12-01 9:48 Ashri, Sarit
2005-12-01 10:17 ` Philippe Gerum
2005-12-01 10:23 ` 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=43933288.8000906@domain.hid \
--to=rpm@xenomai.org \
--cc=Sashri@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.