From: Tom Zanussi <tom.zanussi@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemtap: remove non-core COMPATIBLE_MACHINES
Date: Mon, 13 Jun 2011 09:54:05 -0500 [thread overview]
Message-ID: <1307976845.10825.5.camel@elmorro> (raw)
In-Reply-To: <05D8A861-D865-4303-BB8B-69F5F22B651D@dominion.thruhere.net>
On Mon, 2011-06-13 at 07:47 -0700, Koen Kooi wrote:
> Op 13 jun 2011, om 16:35 heeft Tom Zanussi het volgende geschreven:
> > -COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuppc|emenlow|crownbay|atom-pc|n450)"
> > +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuppc|atom-pc)"
>
> After having looked at the recipe (basically 'inherit autotools', PACKAGE_ARCH = BASE_PACKAGE_ARCH) and reading the systemtap wiki I can't figure out why COMPATIBLE_MACHINE is actually needed. The closest I get is "needs specific kernel config", but that argument quickly falls down when looking at other recipes that need that (e.g. udev) and considering out layer strategy (bbappending it for all your machines).
>
> So, what am I missing here?
>
My testing showed systemtap doesn't actually work on arm, and has no
support for mips - the machines listed are the only ones I've been able
to verify that work.
Tom
> regards,
>
> Koen
>
> PS: there's no 'atom-pc' in OE-core
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-13 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 14:35 [PATCH] systemtap: remove non-core COMPATIBLE_MACHINES Tom Zanussi
2011-06-13 14:47 ` Koen Kooi
2011-06-13 14:48 ` Koen Kooi
2011-06-13 14:54 ` Tom Zanussi [this message]
2011-06-13 15:12 ` Koen Kooi
2011-06-13 15:17 ` Tom Zanussi
2011-06-13 15:12 ` Phil Blundell
-- strict thread matches above, loose matches on Subject: below --
2011-06-14 22:51 Tom Zanussi
2011-06-16 21:14 ` Richard Purdie
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=1307976845.10825.5.camel@elmorro \
--to=tom.zanussi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox