Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5900] New: config flags to the Xenomai build system ...
Date: Mon,  4 Feb 2013 21:53:25 +0000 (UTC)	[thread overview]
Message-ID: <bug-5900-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=5900

           Summary: config flags to the Xenomai build system ...
           Product: buildroot
           Version: 2012.05
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Outdated package
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: raespi at icid.cu
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


The only two options passed to the xenomai package in the
package/xenomai/xenomai.mk are:

ifeq ($(BR2_PACKAGE_XENOMAI_SMP),y)
XENOMAI_CONF_OPT += --enable-smp
endif

XENOMAI_CONF_OPT += --includedir=/usr/include/xenomai/

On my target arch ( smdk2440 / s3c24xx ) I need these also:
XENOMAI_CONF_OPT += CFLAGS="-march=armv4t -msoft-float" LDFLAGS="-march=armv4t
-msoft-float"

without them, the xenomai test suite fails to detect any FPU support at all,
even if it's emulated by software such as this case.  It's something that needs
to be passed to the ./configure according to their "Getting Started" document,
and something that has been discussed recently in their mailing lists ...

I know it can't be passed on like this exactly, but maybe with a conditional
block for this architecture.  Here are the options by arch that you should pass
( taken from the Xenomai site ):

at91rm9200     :: CFLAGS="-march=armv4t -msoft-float"
at91sam9x      :: CFLAGS="-march=armv5 -msoft-float"
imx1           :: CFLAGS="-march=armv4t -msoft-float"
imx21          :: CFLAGS="-march=armv5 -msoft-float"
imx31          :: CFLAGS="-march=armv6 -mfpu=vfp"
imx51/imx53    :: CFLAGS="-march=armv7-a -mfpu=vfp3"
imx6q          :: CFLAGS="-march=armv7-a -mfpu=vfp3"
ixp4xx         :: CFLAGS="-march=armv5 -msoft-float" --enable-arm-tsc=ixp4xx
omap3          :: -march=armv7-a -mfpu=vfp3
omap4          :: -march=armv7-a -mfpu=vfp3
orion          :: -march=armv5 -mfpu=vfp
pxa            :: -march=armv5 -msoft-float
pxa3xx         :: CFLAGS="-march=armv5 -msoft-float"
--enable-arm-quirks=xscale3
s3c24xx        :: CFLAGS="-march=armv4t -msoft-float"
sa1100         :: CFLAGS="-march=armv4t -msoft-float"
--enable-arm-quirks=sa1100

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-02-04 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 21:53 bugzilla at busybox.net [this message]
2013-02-04 21:53 ` [Buildroot] [Bug 5900] config flags to the Xenomai build system bugzilla at busybox.net
2013-02-04 21:57 ` bugzilla at busybox.net
2013-02-04 22:05 ` bugzilla at busybox.net
2013-02-04 22:31 ` bugzilla at busybox.net
2013-02-05 14:41 ` bugzilla at busybox.net
2014-05-18 19:26 ` bugzilla at busybox.net
2014-07-16 19:38 ` bugzilla at busybox.net
2014-07-16 20:00   ` Yann E. MORIN
2014-07-22 21:22 ` bugzilla at busybox.net
2014-07-30 20:05 ` bugzilla at busybox.net

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=bug-5900-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox