All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Charlton, John" <john.charlton@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] pthread_setschedparam: Function not implemented
Date: Thu, 13 Aug 2009 17:12:44 +0200	[thread overview]
Message-ID: <4A842D6C.5000106@domain.hid> (raw)
In-Reply-To: <CF7FB0793253794F9F45991443E5FE20060F03FB23@domain.hid>

Charlton, John wrote:
> >  
> > 
> > -----Original Message-----
> > From: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org] 
> > Sent: Thursday, August 13, 2009 9:17 AM
> > To: Charlton, John
> > Cc: xenomai@xenomai.org
> > Subject: Re: [Xenomai-help] pthread_setschedparam: Function not implemented
> >> These are the flags passed for "FULL_OPTIMAZATION". Obviously, one of 
> >> these optimizations messes up xenomai. In fact, if you look at the 
> >> Makefile, -O2 is used for the user programs, but not for the skins 
> >> libraries.
> >>
> >> The bitbake recipe now includes the following lines:
> >> # set CFLAGS and CXXFLAGS to ${CPPFLAGS} so that they just have the 
> >> appropirate -isystem flag, but no of the other -f flags, as they break 
> >> the posix skin library build export CFLAGS="${CPPFLAGS}"
> >> export CXXFLAGS="${CPPFLAGS}"
> >> export TARGET_CFLAGS="${CFLAGS}"
> >> export TARGET_CXXFLAGS="${CXXFLAGS}"
> >> ./configure --build=i686-angstrom-linux
> > 
> > This is wrong. Passing the flags to configure using environment variable is deprecated since even before the birth of the Xenomai project.
> > TARGET_CFLAGS and TARGET_CXXFLAGS are not used anywhere by Xenomai build system.

Please stop answering below the '-- ' token, as this token is used to
separate the mail body from the signature, and since you post below it,
my mail client considers (rightly) your answer as a signature and strips
it when I try replying to you. So, I have to spend some time manually
reformatting your answer as you should have formatted it in the first place.

>
> How does the xenomai configure script get the correct cross compiler
> settings?  Is it just a matter of using --host to specify the target
> cross compiler?
> ./configure --host=i686-angstrom-linux
>
> I had some problems early on when the xenomai configure script would
> use the build system compiler rather than the cross compiler.
> Obviously the cross compiler has to be in the build environment path
> environment.  Is it best to leave all other compiler flags unset when
> running configure?

You can pass arguments to configure, but on its command line, not using
environment variables. For instance:

./configure --host=i686-angstrom-linux CPPFLAGS=${CPPFLAGS}

And yes, the toolchain executables names are deduced from the value
passed to the --host flag. But you can override them on configure
command line too:

./configure --host=i686 CC=i686-angstrom-linux-gcc

etc...

-- 
                                          Gilles



      reply	other threads:[~2009-08-13 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 19:38 [Xenomai-help] pthread_setschedparam: Function not implemented Charlton, John
2009-08-11 19:45 ` Gilles Chanteperdrix
2009-08-11 20:02   ` Gilles Chanteperdrix
2009-08-12 15:05     ` Charlton, John
2009-08-12 15:15       ` Gilles Chanteperdrix
2009-08-12 18:29         ` Charlton, John
2009-08-12 18:57           ` Gilles Chanteperdrix
2009-08-12 19:08             ` Charlton, John
2009-08-12 19:15               ` Gilles Chanteperdrix
2009-08-13 11:26                 ` Charlton, John
2009-08-13 11:31                   ` Gilles Chanteperdrix
2009-08-13 13:00                     ` Charlton, John
2009-08-13 13:17                       ` Gilles Chanteperdrix
2009-08-13 15:04                         ` Charlton, John
2009-08-13 15:12                           ` Gilles Chanteperdrix [this message]

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=4A842D6C.5000106@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=john.charlton@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.