From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
Date: Wed, 30 May 2012 10:00:30 -0500 [thread overview]
Message-ID: <4FC6360E.1010007@windriver.com> (raw)
In-Reply-To: <559834C0-53F2-4E17-8A48-4061CDB0B63B@gmail.com>
On 5/30/12 9:47 AM, Elvis Dowson wrote:
> Hi Khem,
>
>> On Tue, May 29, 2012 at 9:56 PM, Khem Raj<raj.khem@gmail.com> wrote:
>>> On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson<elvis.dowson@gmail.com> wrote:
>>>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc440"
>>>
>>> may be this should be be
>>>
>>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"
>>>
>>> other pieces look good
>
>
> What does the -nf suffix do ?
-nf means "no floating" point math.
There are variants of the ppc4xx lines with and without classic Power floating
point units.
--Mark
> Best regards,
>
> Elvis Dowson
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2012-05-30 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 18:20 meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440 Elvis Dowson
2012-05-29 18:36 ` Mark Hatle
2012-05-29 19:46 ` Elvis Dowson
2012-05-30 2:56 ` Khem Raj
2012-05-30 14:36 ` Adrian Alonso
2012-05-30 14:47 ` Elvis Dowson
2012-05-30 15:00 ` Khem Raj
2012-05-30 15:34 ` Elvis Dowson
2012-05-30 16:04 ` Khem Raj
2012-05-30 15:00 ` Mark Hatle [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=4FC6360E.1010007@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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.