All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Xenomai core <Xenomai-core@domain.hid>
Subject: [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2.
Date: Tue, 22 Dec 2009 11:06:33 +0100	[thread overview]
Message-ID: <4B309A29.6030405@domain.hid> (raw)


Hi,

Since I started talking about it, I have run build tests fixing a few
things here and there. The current status is this (still at the same
place: http://sisyphus.hd.free.fr/~gilles/bx):

* analogy: I have tried to disable some parts of analogy when compiling
on machines without CONFIG_PCI, as compiling parts using PCI on a
machine without PCI support, give various levels of warning and even
errors depending on the architecture. Doing this, I stumbled across this
compilation error:
http://sisyphus.hd.free.fr/~gilles/bx/beagle/2.6.28-arm-none-linux-gnueabi-gcc-4.3.3/log.html#1
this is with CONFIG_NI_MIO, but without CONFIG_NI_MITE.

So, Alex, could you:
- fix that error, if this combination is supposed to make sense
- fix the Kconfig/Makefile so that no PCI code is compiled if CONFIG_PCI
is not set (I tried and do this myself, but better one who knows than
100 who have to search...). As I said, doing this result in various
levels of success depending on the architecture.

* blackfin: I finally compiled blackfin! had to build a toolchain for
that as the binary-only toolchain from analog.com uses glibc 2.8 and
mine is 2.7. However, blackfin does not compile very well, as can be
seen by the log:
http://sisyphus.hd.free.fr/~gilles/bx/bf537-stamp/2.6.30-bfin-uclinux-gcc-4.1.2/log.html#1
It may happen that my toolchain is buggy or outdated though.

* rtcan: on blackfin we seem to have a conflict with rtcan.
The warning is about CAN_ERR_MASK, sure blackfin is a bit strange to
define this in core headers which are included everywhere. This said,
not prefixing a Xenomai symbol with something like XN seems to be asking
for trouble. Wolfgang, do you think it would be possible to rename the
symbols with such prefix? Or do you share some code with socket-can that
you do not want to touch?

* nios2: I am lacking some important file needed to even start to compile.

Thanks in advance for your efforts.
Regards.

-- 
					    Gilles.


             reply	other threads:[~2009-12-22 10:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 10:06 Gilles Chanteperdrix [this message]
2009-12-22 10:43 ` [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2 Philippe Gerum
2009-12-22 11:36 ` Jan Kiszka
2009-12-22 11:45   ` Gilles Chanteperdrix
2009-12-22 11:50     ` Wolfgang Grandegger
2009-12-22 11:55     ` Wolfgang Grandegger
2009-12-22 12:30       ` Gilles Chanteperdrix
2009-12-22 12:43         ` Jan Kiszka
2009-12-22 12:46           ` Gilles Chanteperdrix
2009-12-22 13:38             ` Wolfgang Grandegger
2009-12-22 13:10 ` Patrice Kadionik
2009-12-22 14:07 ` Patrice Kadionik
2009-12-23 12:16   ` Gilles Chanteperdrix
2009-12-23  1:03 ` Alexis Berlemont
2009-12-23 12:32   ` Gilles Chanteperdrix
2009-12-26  0:09     ` Alexis Berlemont
2009-12-26 18:09       ` Gilles Chanteperdrix
2009-12-26 18:27         ` Philippe Gerum
2009-12-26 22:54           ` Gilles Chanteperdrix
2009-12-27  0:22             ` 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=4B309A29.6030405@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    /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.