From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Eder Alves de Moura <edermoura@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Compiling testsuite and utils
Date: Fri, 8 Jul 2016 21:49:05 +0200 [thread overview]
Message-ID: <20160708194905.GQ9465@hermes.click-hack.org> (raw)
In-Reply-To: <CAPXCTbbQ1Lo7voRB1sVOtnZ0yjwhZBgUnzi1YX2rv_CL1z8f0g@mail.gmail.com>
On Fri, Jul 08, 2016 at 04:30:17PM -0300, Eder Alves de Moura wrote:
> Dears,
>
> I am starting with Xenomai and rt systems and I want to compile it for
> a raspberry pi 2/3 and beaglebone black but first I compiled it to a
> PC and, apparently it is working fine.
>
> $ dmesg | grep -i xenomai
> [ 3.224489] [Xenomai] scheduling class idle registered.
> [ 3.224491] [Xenomai] scheduling class rt registered.
> [ 3.224515] [Xenomai] disabling automatic C1E state promotion on
> Intel processor
> [ 3.224521] [Xenomai] SMI-enabled chipset found, but SMI workaround disabled
> (see xenomai.smi parameter). You might encounter
> [ 3.224592] I-pipe: head domain Xenomai registered.
> [ 3.224916] [Xenomai] Cobalt v3.0.2 (Exact Zero)
>
>
>
> But after install I could not compile the tools for xenomai, running
>
> $ mkdir $build_root && cd $build_root
> $ $xenomai_root/configure --with-core=cobalt --enable-smp --enable-pshared \
> --host=i686-linux CFLAGS="-m32 -O2" LDFLAGS="-m32"
>
> I am receiving the following message
>
> checking whether we build for Cobalt or Mercury core... cobalt
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for i686-linux-gcc... no
> checking for gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/home/pc/tools/xenomai-3-3.0.2':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
Are you sure you have everything installed for gcc -m32 to work? I
mean, did you try to compile an "hello world" application with gcc
-m32 to see if the compilation works? Also, what is the point of
compiling in 32 bits mode, why not using a 64 bits kernel and
user-space?
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-07-08 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 19:30 [Xenomai] Compiling testsuite and utils Eder Alves de Moura
2016-07-08 19:40 ` Philippe Gerum
2016-07-08 19:49 ` Gilles Chanteperdrix [this message]
[not found] ` <CAPXCTbYJ_rQnvdU7srw1oGL6R0c7vJmMF+u_T7d-zgkZ1yLCXg@mail.gmail.com>
2016-07-08 20:34 ` Gilles Chanteperdrix
2016-07-08 20:47 ` Eder Alves de Moura
2016-07-08 20:50 ` Gilles Chanteperdrix
2016-07-09 0:04 ` Eder Alves de Moura
2016-07-09 2:09 ` Gilles Chanteperdrix
2016-07-08 20:48 ` 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=20160708194905.GQ9465@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=edermoura@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.