From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: inflo <inflo@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] xenomai user lib build error
Date: Thu, 02 Dec 2010 00:08:28 +0100 [thread overview]
Message-ID: <4CF6D56C.4040203@domain.hid> (raw)
In-Reply-To: <20101201193518.7c2ed21c.inflo@domain.hid>
inflo wrote:
> hi, the code compiles without errors. I got it once compiled, but
> after replaying what i have done, it wont work again :(
Ok. Send me the result of this code compiled with
powerpc-linux-gnu-gcc -E.
>
> The prepare-kernel.sh script i can call from whereever i am, i mean,
> i could go to e.g. /tmp and could call
>
> /usr/src/xenomai-2.5.5.2/scripts/prepare-kernel.sh --arch=powerpc
> --adeos=/usr/src/xenomai-2.5.5.2/ksrc/arch/powerpc/patches/adeos-ipipe-2.6.35.7-ppc-1.5-*.patch
> --linux=/usr/src/linux-2.6.35.7
>
> then i could go cd /usr/src/linux-2.6.35.7 and configure and build
> the kernel from within this directory ? whats with this linux/ shadow
> copy ?
prepare-kernel does not make a shadow copy, it modifies
/usr/src/linux-2.6.35.7 in place. So, if you have linux/ it comes from
somewhere else.
>
> After building patched kernel, i need to configure xenomai user libs.
> This is done from whereever i want? i mean, i could go to e.g. /tmp
> and call
>
> /usr/src/xenomai-2.5.5.2/configure --host=powerpc-linux-gnu and then
> also call inside this dir
>
> make
>
> to build xenomai libs?
Yes, you can do that, though I would recommend to do it in something like
/tmp/xenomai-build in order to avoid polluting /tmp with the compilation
files.
>
> The user libs build fails mostly with the same procedure deleting
> linux/ copying linux source to linux/ hanging
>
> my cross tools are prefixed with powerpc-linux-gnu- like
> powerpc-linux-gnu-gcc
Yes, and this compilation failure probably has other reasons than
installation directories names. This is a problem of what Xenomai source
expects and the way your toolchain/libc headers are made.
If in the program I asked you to compile you replace #include <errno.h>
with #include <linux/errno.h>, does it still compile?
--
Gilles.
next prev parent reply other threads:[~2010-12-01 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 18:50 [Xenomai-help] xenomai user lib build error inflo
2010-11-29 20:29 ` Gilles Chanteperdrix
2010-12-01 18:35 ` inflo
2010-12-01 23:08 ` Gilles Chanteperdrix [this message]
2010-12-02 18:17 ` inflo
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=4CF6D56C.4040203@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=inflo@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.