From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v3 1/1] nodejs: cleanup and update
Date: Tue, 22 Dec 2015 10:29:47 -0500 [thread overview]
Message-ID: <56796C6B.9070002@gmail.com> (raw)
In-Reply-To: <CAJ86T=X7-FxDqTZ1fJgx-sQaVUjM+Xe-E_QXe1QfXfgQMptLww@mail.gmail.com>
Hi Andre,
On 12/22/15 04:35, Andre McCurdy wrote:
> Here's the link to the "official" announcement about v8 dropping
> support for ARM cores without vfp2 support:
Thanks, I'll include that in v4.
> +COMPATIBLE_MACHINE = "(-)"
> +COMPATIBLE_MACHINE_x86 = "(.*)"
> +COMPATIBLE_MACHINE_x86-64 = "(.*)"
> +COMPATIBLE_MACHINE_armv7a = "(.*)"
> Please blacklist armv4 and armv5 instead of whitelisting armv7a (armv6
> and potential future arm targets such as armv7ve are still expected to
> work. It's only armv4 and armv5 which are not).
That was what I was trying to do :-) I don't have much experience in
this, I've been asking on IRC and the mailing lists, and there aren't
many examples to copy. I think the following works:
COMPATIBLE_MACHINE_armv4 = "(!.*armv4).*"
COMPATIBLE_MACHINE_armv5 = "(!.*armv5).*"
COMPATIBLE_MACHINE_mips64 = "(!.*mips64).*"
?
Best regards,
Trevor
next prev parent reply other threads:[~2015-12-22 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 4:27 [meta-oe][PATCH v3 0/1] nodejs cleanup and update Trevor Woerner
2015-12-22 4:27 ` [meta-oe][PATCH v3 1/1] nodejs: " Trevor Woerner
2015-12-22 9:35 ` Andre McCurdy
2015-12-22 15:29 ` Trevor Woerner [this message]
2015-12-22 15:49 ` Martin Jansa
2015-12-22 16:00 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 4:10 [meta-oe][PATCH v3 0/1] nodejs " Trevor Woerner
2015-12-22 4:10 ` [meta-oe][PATCH v3 1/1] nodejs: " Trevor Woerner
2015-12-22 4:24 ` Trevor Woerner
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=56796C6B.9070002@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-devel@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.