All of lore.kernel.org
 help / color / mirror / Atom feed
From: raespi <raespi@icid.cu>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] about switchtest ...
Date: Tue, 05 Feb 2013 10:18:43 -0500	[thread overview]
Message-ID: <511122D3.8000501@icid.cu> (raw)
In-Reply-To: <51111E46.4070706@xenomai.org>

Yes I saw your answer and understood what you were talking about.  
Again, the "-march=armv4t -msoft-float" options are passed to every 
package Buildroot builds since it's an option I enable in the Buildroot 
config file.  The problem may lie in how it passes them to Xenomai 
specifically.  For a fact, I can assure you they weren't passed to the 
right of the ./configure script as you suggested since I double checked 
the config.log for the Xenomai build.   Why the "Illegal Instruction" 
message wasn't showing up I don't know but it's not something that 
popped up to me before for not passing the flags, at least not in the 
smdk2440 target.

Facts:
1- Buildroot doesn't build correctly the Xenomai package ( test suite 
fails to launch )
2- When passing the flags in Buildroot manually ( for now ) to the 
Xenomai package the test suite runs normally
3- The solution is either fixing the parameter passing scheme on Xenomai 
or how Buildroot passes the parameters ( I go with this last one ).

El 02/05/2013 09:59 AM, Gilles Chanteperdrix escribió:
> On 02/05/2013 03:56 PM, raespi wrote:
>
>> The problem was fixed ... The buildroot system didn't pass the specific
>> CFLAGS and LDFLAGS for my machine.  In your Getting Started guide this
>> is something necessary.  That's what fixed the problem and allowed me to
>> run the tests.  What I'm checking with him is how those flags are passed
>> to Xenomai.  Perhaps he didn't notice it before since no one ran the
>> test suite for this machine ?? IDK ...
>
> No, read my answer again. If buildroot did not pass correct CFLAGS or
> LDFLAGS, you would get an "illegal instruction" trap. So, you have not
> really understood what your problem is, and you have not understood why
> passing specific CFLAGS and LDFLAGS in addition to the ones passed by
> buildroot fixes it.
>




  reply	other threads:[~2013-02-05 15:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 18:28 [Xenomai] about switchtest raespi
2013-02-04 18:31 ` Gilles Chanteperdrix
2013-02-04 19:22   ` raespi
2013-02-04 19:55     ` Gilles Chanteperdrix
2013-02-04 20:30       ` Jan Kiszka
2013-02-04 21:14         ` Gilles Chanteperdrix
     [not found]       ` <511021FC.7080906@icid.cu>
2013-02-04 21:07         ` Gilles Chanteperdrix
2013-02-04 21:28           ` raespi
2013-02-05 13:34             ` raespi
2013-02-05 14:26               ` Gilles Chanteperdrix
2013-02-05 14:52               ` Gilles Chanteperdrix
2013-02-05 14:56                 ` raespi
2013-02-05 14:59                   ` Gilles Chanteperdrix
2013-02-05 15:18                     ` raespi [this message]
2013-02-05 15:25                       ` Gilles Chanteperdrix
2013-02-05 15:31                         ` raespi
2013-02-05 15:32                           ` Gilles Chanteperdrix
2013-02-05 15:38                             ` raespi
2013-02-05 15:58                               ` 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=511122D3.8000501@icid.cu \
    --to=raespi@icid.cu \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.