All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
	openbmc@lists.ozlabs.org
Subject: Re: [oe] [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe
Date: Thu, 31 May 2018 21:37:28 -0700	[thread overview]
Message-ID: <CAMKF1sr-k=TK-wyUtDJMUT8DK=EcS3A08jCJD-xjOD_Aw-MbQw@mail.gmail.com> (raw)
In-Reply-To: <1527820565.499695.1392530280.7147CEB3@webmail.messagingengine.com>

On Thu, May 31, 2018 at 7:36 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> Hi Khem,
>
> Thanks for testing.
>
> On Fri, 1 Jun 2018, at 02:18, Khem Raj wrote:
>> fails to build on qemumips
>>
>
> Do I have to support MIPS for the recipe to be acceptable? Is there some way we can limit the recipe to architectures for which the software is known to work?

Ideally we tend to support the core architectures and mips is one of
them, so unless there is a very basic
reason e.g. missing support etc. we tend to fix the problems, so I
would suggest to see if it can be fixed preferably
if not then we should cite the reason and probably we can add mips to
incompatible hosts but that is last resort
once a recipe goes in it becomes a maintenance work and I would like
to make it as light as possible.

WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openbmc@lists.ozlabs.org,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe
Date: Thu, 31 May 2018 21:37:28 -0700	[thread overview]
Message-ID: <CAMKF1sr-k=TK-wyUtDJMUT8DK=EcS3A08jCJD-xjOD_Aw-MbQw@mail.gmail.com> (raw)
In-Reply-To: <1527820565.499695.1392530280.7147CEB3@webmail.messagingengine.com>

On Thu, May 31, 2018 at 7:36 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> Hi Khem,
>
> Thanks for testing.
>
> On Fri, 1 Jun 2018, at 02:18, Khem Raj wrote:
>> fails to build on qemumips
>>
>
> Do I have to support MIPS for the recipe to be acceptable? Is there some way we can limit the recipe to architectures for which the software is known to work?

Ideally we tend to support the core architectures and mips is one of
them, so unless there is a very basic
reason e.g. missing support etc. we tend to fix the problems, so I
would suggest to see if it can be fixed preferably
if not then we should cite the reason and probably we can add mips to
incompatible hosts but that is last resort
once a recipe goes in it becomes a maintenance work and I would like
to make it as light as possible.


  reply	other threads:[~2018-06-01  4:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10  6:37 [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Andrew Jeffery
2018-05-10  6:37 ` Andrew Jeffery
2018-05-10  6:37 ` [meta-python][PATCH v2 2/3] meta-python: Port python-pyflame to 32-bit ARM Andrew Jeffery
2018-05-10  6:37   ` Andrew Jeffery
2018-05-10  6:37 ` [meta-python][PATCH v2 3/3] meta-python: Make python-pyflame cope with prelinked ELFs Andrew Jeffery
2018-05-10  6:37   ` Andrew Jeffery
2018-05-29 11:48 ` [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Andrew Jeffery
2018-05-29 11:48   ` Andrew Jeffery
2018-05-29 17:04   ` [oe] " Khem Raj
2018-05-29 17:04     ` Khem Raj
2018-05-29 22:03     ` [oe] " Andrew Jeffery
2018-05-29 22:03       ` Andrew Jeffery
2018-05-29 22:23       ` [oe] " Khem Raj
2018-05-29 22:23         ` Khem Raj
2018-05-29 22:29         ` [oe] " Andrew Jeffery
2018-05-29 22:29           ` Andrew Jeffery
2018-05-31 16:48   ` [oe] " Khem Raj
2018-05-31 16:48     ` Khem Raj
2018-06-01  2:36     ` [oe] " Andrew Jeffery
2018-06-01  2:36       ` Andrew Jeffery
2018-06-01  4:37       ` Khem Raj [this message]
2018-06-01  4:37         ` Khem Raj
2018-06-01  5:52         ` [oe] " Andrew Jeffery
2018-06-01  5:52           ` Andrew Jeffery
2018-06-22 21:12           ` [oe] " Khem Raj
2018-06-22 21:12             ` Khem Raj
2018-09-04  9:38     ` [oe] " Martin Jansa
2018-09-04  9:38       ` Martin Jansa
2018-09-04 18:51       ` [oe] " Khem Raj
2018-09-04 18:51         ` Khem Raj
2018-09-10 18:43       ` [meta-python][PATCH] python-pyflame: skip for aarch64 as well Martin Jansa

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='CAMKF1sr-k=TK-wyUtDJMUT8DK=EcS3A08jCJD-xjOD_Aw-MbQw@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --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.