From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: JAY KOTHARI <jaikothari10@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] /asm/ipipe.h not found
Date: Wed, 10 Dec 2014 11:38:29 +0100 [thread overview]
Message-ID: <20141210103829.GA1524@hermes.click-hack.org> (raw)
In-Reply-To: <CALe7ZU07e_Pi4=jbV9y1zuVd4RAKZGRsuUdQrVqWCjPcmjTkgg@mail.gmail.com>
On Wed, Dec 10, 2014 at 03:57:44PM +0530, JAY KOTHARI wrote:
> Hello,
> I am porting linux-3.2.21(xenomai-2.6.2 patched to it) on
> BeagleBoard-XM.
You do not need to port it, it is already supported.
Also, why using such old versions ? The latest version of Xenomai is
2.6.4 and will work with the I-pipe patch for Linux 3.2.21.
> zImage is successfully made. But when I am building
> the modules with following command
>
> $make -j 8 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi modules
>
> It shows error:
> make CONFIG_DEBUG_SECTION_MISMATCH=y
Yes, this has been reported, and fixed in later patches. That is
what you get by using old patches. Simply turn that off.
>
> After this I ran
> $make CONFIG_DEBUG_SECTION_MISMATCH=y
>
> This lets to another error
> include/linux/ipipe.h :33:23: fatal error:asm/ipipe.h: No such file or
> directory.
> compilation terminated.
>
> Actually ipipe.h is there in /asm/ipipe.h:I tried to set CFLAG
> and export it but it is not working.Help would be appreciated.
You do not provide enough information for us to answer that
question. Sorry.
--
Gilles.
next prev parent reply other threads:[~2014-12-10 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 10:27 [Xenomai] /asm/ipipe.h not found JAY KOTHARI
2014-12-10 10:38 ` Gilles Chanteperdrix [this message]
2014-12-10 10:54 ` JAY KOTHARI
2014-12-10 10:58 ` Gilles Chanteperdrix
2014-12-10 11:03 ` Gilles Chanteperdrix
2014-12-10 12:46 ` JAY KOTHARI
2014-12-10 13:09 ` 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=20141210103829.GA1524@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jaikothari10@gmail.com \
--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.