All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] fio: Add PACKAGECONFIG for numa, re-enable ARM build
Date: Fri, 17 Jul 2015 16:45:13 +0200	[thread overview]
Message-ID: <55A914F9.2010204@gmx.de> (raw)
In-Reply-To: <CAJ86T=XoRKBHyH0HmDv9thHr8qSievRt-WwT=qddsUkuyg5qpA@mail.gmail.com>

Hi Andre,

On 2015-07-17 02:46, Andre McCurdy wrote:
>> +PACKAGECONFIG[numa] = ",--disable-numa,numactl"
> 
> I don't think this change will work.
> 
> The fio recipe doesn't use autotools, so the --disable-numa option set
> via PACKAGECONFIG isn't going to have any effect unless you also
> manually pass EXTRA_OECONF into the build somehow.

Ouch, you're right. The configure script is currently only called
indirectly (from the Makefile) and without arguments during do_compile.

How about adding this simple do_configure function?

do_configure() {
    ${B}/configure ${EXTRA_OECONF}
}

>>  # ARM does not currently support NUMA
>> -COMPATIBLE_HOST = "^((?!arm).*)$"
>> +PACKAGECONFIG_remove_arm = "numa"
> 
> In general, it would be better to use something like:
> 
>   PACKAGECONFIG_NUMA = "numa"
>   PACKAGECONFIG_NUMA_arm = ""
> 
>   PACKAGECONFIG ??= "${PACKAGECONFIG_NUMA}"
> 
> _remove can be a little difficult to 'over-ride', so makes things
> harder if someone did, one day, want to experiment with enabling that
> option from local.conf or a .bbappend.

Good point. I thought the _remove was ugly, but it didn't occur to me to
use an additional level of indirection like this.


Dominic


  reply	other threads:[~2015-07-17 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 12:45 [meta-oe][PATCH] fio: Add PACKAGECONFIG for numa, re-enable ARM build Dominic Sacré
2015-07-17  0:46 ` Andre McCurdy
2015-07-17 14:45   ` Dominic Sacré [this message]
2015-07-17 20:56     ` Andre McCurdy
2015-07-17 22:57       ` [meta-oe][PATCH v2] " Dominic Sacré

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=55A914F9.2010204@gmx.de \
    --to=dominic.sacre@gmx.de \
    --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.