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 11:00:47 -0500 [thread overview]
Message-ID: <567973AF.2090905@gmail.com> (raw)
In-Reply-To: <20151222154940.GA2556@jama>
Hi Martin,
On 12/22/15 10:49, Martin Jansa wrote:
>> 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).*"
>>
>> ?
> It's not nice but you can use:
> COMPATIBLE_MACHINE_arm = "(.*)"
> COMPATIBLE_MACHINE_armv4 = "(-)"
> COMPATIBLE_MACHINE_armv5 = "(-)"
> COMPATIBLE_MACHINE_mips64 = "(-)"
>
> If these 3 are the only 3 unsupported, then you can drop override for
> x86, x86-64, arm and change the default to (.*).
Okay, those look like they might work too. I build-tested[1] the
COMPATIBLE_MACHINE lines I proposed and the build did what I wanted it
to do against the 12 I tried. I get the feeling the ones I proposed
might do better against things like "armv5te" and those sorts of
variants? But I'm happy to send a v5 if yours (or something else) are
better.
Best regards,
Trevor
[1] I run-tested them yesterday, so I probably don't have to re-do that
test
prev parent reply other threads:[~2015-12-22 16:00 UTC|newest]
Thread overview: 6+ 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
2015-12-22 15:49 ` Martin Jansa
2015-12-22 16:00 ` Trevor Woerner [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=567973AF.2090905@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox